Enable a network-trigger change of network slices

ABSTRACT

Methods, systems, and devices for wireless communication are described. A method may include determining to modify current-allowed network slices used by a user equipment (UE) based on a network-trigger; identifying new-allowed network slices for the UE based on the determining; selecting a target access and mobility management function (AMF) based on the new-allowed network slices, the target AMF is accessible by the source AMF; and triggering an AMF relocation based on the selecting.

CROSS REFERENCES

The present Application for Patent claims priority to U.S. ProvisionalPatent Application No. 62/505,904 by Faccin, et al., entitled “Enable ANetwork-Trigger Change of Network Slices,” filed May 13, 2017, assignedto the assignee hereof.

INTRODUCTION

The following relates generally to wireless communication, and morespecifically to enable a network-trigger change of network slices.

Wireless communications systems are widely deployed to provide varioustypes of communication content such as voice, video, packet data,messaging, broadcast, and so on. These systems may be capable ofsupporting communication with multiple users by sharing the availablesystem resources (e.g., time, frequency, and power). Examples of suchmultiple-access systems include code division multiple access (CDMA)systems, time division multiple access (TDMA) systems, frequencydivision multiple access (FDMA) systems, and orthogonal frequencydivision multiple access (OFDMA) systems, (e.g., a Long Term Evolution(LTE) system, or a New Radio (NR) system). A wireless multiple-accesscommunications system may include a number of base stations or accessnetwork nodes, each simultaneously supporting communication for multiplecommunication devices, which may be otherwise known as user equipment(UE). In some examples, of the wireless communications systems, a UE mayuse one or more network slices. A network slice is a logical networkincluding Radio Access Network (RAN) and Core Network (CN). A networkslice provides services and network capabilities, which may vary or bethe same from network slice to network slice. A UE may access multiplenetwork slices simultaneously through a RAN.

SUMMARY

A method for wireless communication at a source access and mobilitymanagement function (AMF) is described. The method may includedetermining to modify current-allowed network slices supported for a UEbased at least in part on a network-trigger; identifying new-allowednetwork slices supported for the UE based at least in part on thedetermining; selecting a target AMF based at least in part on thenew-allowed network slices, the target AMF is accessible by the sourceAMF; and triggering an AMF relocation based at least in part on theselecting.

An apparatus for wireless communication is described. The apparatus mayinclude means for determining to modify current-allowed network slicessupported for a UE based at least in part on a network-trigger; meansfor identifying new-allowed network slices supported for the UE based atleast in part on the determining; means for selecting a target AMF basedat least in part on the new-allowed network slices, the target AMF isaccessible by the source AMF; and means for triggering an AMF relocationbased at least in part on the selecting.

Another apparatus for wireless communication is described. The apparatusmay include a processor, memory in electronic communication with theprocessor. The processor and memory may be configured to determine tomodify current-allowed network slices supported for a UE based at leastin part on a network-trigger; identify new-allowed network slicessupported for the UE based at least in part on the determining; select atarget AMF based at least in part on the new-allowed network slices, thetarget AMF is accessible by the source AMF; and trigger an AMFrelocation based at least in part on the selecting.

A non-transitory computer readable medium for wireless communication isdescribed. The non-transitory computer-readable medium may includeinstructions operable to cause a processor to determine to modifycurrent-allowed network slices supported for a UE based at least in parton a network-trigger; identify new-allowed network slices supported forthe UE based at least in part on the determining; select a target AMFbased at least in part on the new-allowed network slices, the target AMFis accessible by the source AMF; and trigger an AMF relocation based atleast in part on the selecting.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for determining that the UE has anactive network slice instance (NSI) associated with at least one networkselection assistance information (NSSAI); and identifying that an activeNSI is supported by the new-allowed network slices. Some examples of themethod, apparatus, and non-transitory computer-readable medium describedabove may further include processes, features, means, or instructionsfor generating a status report indicating a status of all existingprotocol data unit (PDU) sessions associated with the active NSI.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above for triggering the AMFrelocation may further include processes, features, means, orinstructions for transmitting an AMF relocation request to the targetAMF based at least in part on the new-allowed NSSAI, the AMF relocationrequest comprises a status of all existing PDU session associated withthe active NSI that are supported and active, or a new radio (NR)globally unique temporary identifier (GUTI), or both.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for triggering a release procedure ofan active PDU session associated with the current-allowed network slicesbased at least in part on identifying that the active PDU session isunsupported by the new-allowed network slices. In some examples of themethod, apparatus, and non-transitory computer-readable medium describedabove, the triggering the release procedure is based at least in part ondirect signaling to the UE.

Another method for wireless communication at a target AMF is described.The method may include receiving, from a source AMF, an AMF relocationrequest for a UE currently served by the source AMF, the AMF relocationrequest comprising new-allowed network slices and UE contextinformation; allocating an updated identifier based at least in part onthe AMF relocation request; and transmitting to the UE a configurationrequest message comprising the updated identifier, an updated status ofan existing PDU session, or the new-allowed network slices, or acombination.

Another apparatus for wireless communication is described. The apparatusmay include means for receiving, from a source network entity, an AMFrelocation request for a UE currently served by the source networkentity, the AMF relocation request comprising new-allowed network slicesand UE context information; means for allocating an updated identifierbased at least in part on the AMF relocation request; and means fortransmitting to the UE a configuration request message comprising theupdated identifier, an updated status of an existing PDU session, or thenew-allowed network slices, or a combination.

Another apparatus for wireless communication is described. The apparatusmay include a processor, memory in electronic communication with theprocessor. The processor and memory may be configured to receive an AMFrelocation request for a UE currently served by a source AMF, the AMFrelocation request comprising new-allowed network slices and UE contextinformation; allocate an updated identifier based at least in part onthe AMF relocation request; and transmit to the UE a configurationrequest message comprising the updated identifier, an updated status ofan existing PDU session, or the new-allowed network slices, or acombination.

Another non-transitory computer readable medium for wirelesscommunication is described. The non-transitory computer-readable mediummay include instructions operable to cause a processor to receive an AMFrelocation request for a UE currently served by a source AMF, the AMFrelocation request comprising new-allowed network slices and UE contextinformation; allocate an updated identifier based at least in part onthe AMF relocation request; and transmit to the UE a configurationrequest message comprising the updated identifier, an updated status ofan existing PDU session, or the new-allowed network slices, or acombination.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, the updated identifiercomprises NR GUTI. In some examples of the method, apparatus, andnon-transitory computer-readable medium described above, the where theUE context information comprises a status of an existing PDU sessionassociated with an active NSI or a current NR GUTI, or a combination.

Another method for wireless communication at a UE is described. Themethod may include receiving, from a source AMF, a configuration messagecomprising an identifier associated with a target AMF, a status ofexisting active PDU sessions of the UE, or new-allowed network slices,or a combination; storing information associated with the new-allowednetwork slices and identifier; identifying an active PDU session basedat least in part on the status of the existing active PDU sessions ofthe configuration message, where the active PDU session is unsupportedby the new-allowed network slices; and locally releasing the active PDUsession.

Another apparatus for wireless communication is described. The apparatusmay include means for receiving, from a source AMF, a configurationmessage comprising an identifier associated with a target AMF, a statusof existing active PDU sessions of the UE, or new-allowed networkslices, or a combination; means for storing information associated withthe new-allowed network slices and identifier; means for identifying anactive PDU session based at least in part on the status of the existingactive PDU sessions of the configuration message, the active PDU sessionis unsupported by the new-allowed network slices; and means for locallyreleasing the active PDU session.

Another apparatus for wireless communication is described. The apparatusmay include a processor, memory in electronic communication with theprocessor. The processor and memory may be configured to receive, from asource AMF, a configuration message comprising an identifier associatedwith a target AMF, a status of existing active PDU sessions of the UE,or new-allowed network slices, or a combination; store informationassociated with the new-allowed network slices and identifier; identifyan active PDU session based at least in part on the status of theexisting active PDU sessions of the configuration message, the activePDU session is unsupported by the new-allowed network slices; andlocally release the active PDU session.

Another non-transitory computer readable medium for wirelesscommunication is described. The non-transitory computer-readable mediummay include instructions operable to cause a processor to receive, froma source AMF, a configuration message comprising an identifierassociated with a target AMF, a status of existing active PDU sessionsof the UE, or new-allowed network slices, or a combination; storeinformation associated with the new-allowed network slices andidentifier; identify an active PDU session based at least in part on thestatus of the existing active PDU sessions of the configuration message,the active PDU session is unsupported by the new-allowed network slices;and locally release the active PDU session.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, the identifier comprises a NRGUTI.

Another method for wireless communication at a source AMF is described.The method may include determining to modify current-allowed networkslices used by a UE based at least in part on a receivednetwork-trigger; identifying new-allowed network slices for the UE basedat least in part on the determining; and determining that a target AMFassociated with the new-allowed network slices is inaccessible by thesource AMF.

Another apparatus for wireless communication is described. The apparatusmay include means for determining to modify current-allowed networkslices used by a UE based at least in part on a receivednetwork-trigger; means for identifying new-allowed network slices forthe UE based at least in part on the determining; and means fordetermining that a target AMF associated with the new-allowed networkslices is inaccessible by the source AMF.

Another apparatus for wireless communication is described. The apparatusmay include a processor, memory in electronic communication with theprocessor. The processor and memory may be configured to determine tomodify current-allowed network slices used by a UE based at least inpart on a received network-trigger; identify new-allowed network slicesfor the UE based at least in part on the determining; and determiningthat a target AMF associated with the new-allowed network slices isinaccessible by apparatus.

Another non-transitory computer readable medium for wirelesscommunication is described. The non-transitory computer-readable mediummay include instructions operable to cause a processor to determine tomodify current-allowed network slices used by a UE based at least inpart on a received network-trigger; identify new-allowed network slicesfor the UE based at least in part on the determining; and determiningthat a target AMF associated with the new-allowed network slices isinaccessible by a source AMF.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for transmitting a de-registrationrequest to the UE based at least in part on determining that the targetAMF is inaccessible by the source AMF. In some examples of the method,apparatus, and non-transitory computer-readable medium described above,the de-registration request comprises an indication to perform are-registration procedure, the new-allowed network slices, or a codeindicating that the de-registration request is in response to a changeof supported network slices, or a combination. Some examples of themethod, apparatus, and non-transitory computer-readable medium describedabove may further include processes, features, means, or instructionsfor triggering a release procedure of an active PDU session associatedwith current-allowed network slices that are unsupported by thenew-allowed network slices; and releasing UE context comprising a statusreport of active PDU session or a NR GUTI, or both based at least inpart on the triggering.

Another method for wireless communication at a UE is described. Themethod may include identifying a re-registration request and a codeindicating a request to register a set of network slices associated witha new-allowed network slice based at least in part on a receivedde-registration request from a source AMF that is serving the UE;identifying the new-allowed network slices based at least in part on thereceived de-registration request; and generating a request forregistering the set of network slices based at least in part on thecode.

Another apparatus for wireless communication is described. The apparatusmay include a means for identifying a re-registration request and a codeindicating a request to register a set of network slices associated witha new-allowed network slice based at least in part on a receivedde-registration request from a source AMF that is serving the UE; meansfor identifying the new-allowed network slices based at least in part onthe received de-registration request; and means for generating a requestfor registering the set of network slices based at least in part on thecode.

Another apparatus for wireless communication is described. The apparatusmay include a processor, memory in electronic communication with theprocessor. The processor and memory may be configured to identify are-registration request and a code indicating a request to register aset of network slices associated with a new-allowed network slice basedat least in part on a received de-registration request from a source AMFthat is serving the UE; identify the new-allowed network slices based atleast in part on the received de-registration request; and generate arequest for registering the set of network slices based at least in parton the code.

A non-transitory computer readable medium for wireless communication isdescribed. The non-transitory computer-readable medium may includeinstructions operable to cause a processor to identify a re-registrationrequest and a code indicating a request to register a set of networkslices associated with a new-allowed network slice based at least inpart on a received de-registration request from a source AMF that isserving the UE; identify the new-allowed network slices based at leastin part on the received de-registration request; and generate a requestfor registering the set of network slices based at least in part on thecode.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for storing information associated withthe new-allowed network slices, where the information comprises NSSAI.Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for removing a current NR GUTI based atleast in part on the code.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, an upper layer of the UEtransmits to a lower layer of the UE: an indication to release aconnection with a RAN and to re-establish the connection, or a NSSAIrequest, or an indication to refrain from providing a NR GUTI, or acombination. In some examples of the method, apparatus, andnon-transitory computer-readable medium described above, the upper layercomprises a non-access stratum (NAS) layer and the lower layer comprisesan AS layer.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for transmitting a request tore-establish the connection based at least in part on the indication tore-establish the connection, where the request comprises the NSSAIrequest. In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, the connection comprises aradio resource control (RRC) connection. In some examples of the method,apparatus, and non-transitory computer-readable medium described above,the UE performs a RRC connection release procedure or an RRC connectionestablishment procedure based at least in part on the indication torelease a connection with a RAN and to re-establish the connection.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, the connection comprises aninternet protocol (IP) security (IPsec) tunnel connection. In someexamples of the method, apparatus, and non-transitory computer-readablemedium described above, the UE performs an IPsec tunnel releaseprocedure or an IPsec tunnel establishment procedure based at least inpart on the indication to release a connection with a RAN and tore-establish the connection.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for transmitting a new RRCreconfiguration request message comprising a the NSSAI request, or acode indicating signaling path configuration, or a current NR GUTI, or acombination. Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for transmitting a Nwu messagecomprising the NSSAI request, or a code indicating signaling pathconfiguration, or a current NR GUTI, or a combination. In some examplesof the method, apparatus, and non-transitory computer-readable mediumdescribed above, the Nwu message comprises an IKEv2 INFORMATIONALmessage, or a reconfigure signaling connection message, or both.

Another method for wireless communication an access network (AN) isdescribed. The method may include receiving, from a UE a RRC connectionrequest comprising NSSAI; identifying a source AMF associated withcurrent-allowed network slices of the UE based at least in part on theNSSAI; determining to modify the NSSAI based at least in part on atrigger indication; identifying new-allowed network slices supported forthe UE based at least in part on the determining; selecting a target AMFto serve the UE based at least in part on the new-allowed networkslices; and triggering an AMF relocation based at least in part on theselecting, where the AMF relocation comprises signaling the source AMFto redirect the RRC connection request to the target AMF.

Another apparatus for wireless communication is described. The apparatusmay include means for receiving, from a UE a RRC connection requestcomprising NSSAI; means for identifying a source AMF associated withcurrent-allowed network slices of the UE based at least in part on theNSSAI; means for determining to modify the NSSAI based at least in parton a trigger indication; means for identifying new-allowed networkslices supported for the UE based at least in part on the determining;means for selecting a target AMF to serve the UE based at least in parton the new-allowed network slices; and means for triggering an AMFrelocation based at least in part on the selecting, where the AMFrelocation comprises signaling the source AMF to redirect the RRCconnection request to the target AMF.

Another apparatus for wireless communication is described. The apparatusmay include a processor, memory in electronic communication with theprocessor. The processor and memory may be configured to receive, from aUE a RRC connection request comprising NSSAI; identify a source AMFassociated with current-allowed network slices of the UE based at leastin part on the NSSAI; determine to modify the NSSAI based at least inpart on a trigger indication; identify new-allowed network slicessupported for the UE based at least in part on the determining; select atarget AMF to serve the UE based at least in part on the new-allowednetwork slices; and trigger an AMF relocation based at least in part onthe selecting, where the AMF relocation comprises signaling the sourceAMF to redirect the RRC connection request to the target AMF.

Another non-transitory computer readable medium for wirelesscommunication is described. The non-transitory computer-readable mediummay include instructions operable to cause a processor to receive, froma UE a RRC connection request comprising NSSAI; identify a source AMFassociated with current-allowed network slices of the UE based at leastin part on the NSSAI; determine to modify the NSSAI based at least inpart on a trigger indication; identify new-allowed network slicessupported for the UE based at least in part on the determining; select atarget AMF to serve the UE based at least in part on the new-allowednetwork slices; and trigger an AMF relocation based at least in part onthe selecting, where the AMF relocation comprises signaling the sourceAMF to redirect the RRC connection request to the target AMF.

Another method for wireless communication is described. The method mayinclude receiving, from a UE a request for relocation from a source AMFassociated with current-allowed network slices of the UE based at leastin part on network slice assistance information; determining to modifythe NSSAI based at least in part on a trigger indication; identifyingnew-allowed network slices supported for the UE based at least in parton the determining; selecting a target AMF to serve the UE based atleast in part on the new-allowed network slices; and triggering an AMFrelocation based at least in part on the selecting, where the AMFrelocation comprises initiating a redirection of the UE from the sourceAMF to the target AMF.

Another apparatus for wireless communication is described. The apparatusmay include means for receiving, from a UE a request for relocation froma source AMF associated with current-allowed network slices of the UEbased at least in part on network slice assistance information; meansfor determining to modify the NSSAI based at least in part on a triggerindication; means for identifying new-allowed network slices supportedfor the UE based at least in part on the determining; means forselecting a target AMF to serve the UE based at least in part on thenew-allowed network slices; and means for triggering an AMF relocationbased at least in part on the selecting, where the AMF relocationcomprises initiating a redirection of the UE from the source AMF to thetarget AMF.

Another apparatus for wireless communication is described. The apparatusmay include a processor, memory in electronic communication with theprocessor. The processor and memory may be configured to receive, from aUE a request for relocation from a source AMF associated withcurrent-allowed network slices of the UE based at least in part onnetwork slice assistance information; determine to modify the NSSAIbased at least in part on a trigger indication; identify new-allowednetwork slices supported for the UE based at least in part on thedetermining; select a target AMF to serve the UE based at least in parton the new-allowed network slices; and trigger an AMF relocation basedat least in part on the selecting, where the AMF relocation comprisesinitiating a redirection of the UE from the source AMF to the targetAMF.

Another non-transitory computer readable medium for wirelesscommunication is described. The non-transitory computer-readable mediummay include instructions operable to cause a processor to receive, froma UE a request for relocation from a source AMF associated withcurrent-allowed network slices of the UE based at least in part onnetwork slice assistance information; determine to modify the NSSAIbased at least in part on a trigger indication; identify new-allowednetwork slices supported for the UE based at least in part on thedetermining; select a target AMF to serve the UE based at least in parton the new-allowed network slices; and trigger an AMF relocation basedat least in part on the selecting, where the AMF relocation comprisesinitiating a redirection of the UE from the source AMF to the targetAMF.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for transmitting an indicationcomprising information for selection of the target AMF for redirectingthe RRC connection request; and transmitting instructions for performingthe redirecting via the source AMF.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for establishing an N2 signalingconnection with the target AMF; and transmitting a NAS message receivedfrom the UE to the target AMF using the N2 signaling connection.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for transmitting, to a previous servingAMF of the UE, a request to release an N2 signaling connection. Someexamples of the method, apparatus, and non-transitory computer-readablemedium described above may further include processes, features, means,or instructions for receiving, from the target AMF, an updated NR GUTIfor the UE; and replacing a previous NR GUTI with the received updatedNR GUTI for the UE.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for receiving, from a target AMF, anupdated NR GUTI for the UE; and replacing the previous NR GUTI with thereceived updated NR GUTI for the UE. Some examples of the method,apparatus, and non-transitory computer-readable medium described abovemay further include processes, features, means, or instructions fortransmitting, to the UE, a configuration request message containing theupdated NR GUTI, a status of existing active PDU sessions of the UE,indication of the modifying to the NSSAI, or a combination.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1 and 2 illustrate examples of a wireless communications systemthat supports enabling a network-trigger change of network slices, inaccordance with one or more aspects of the present disclosure.

FIGS. 3 and 4 illustrate examples of a process flow that supportsenabling a network-trigger change of network slices, in accordance withone or more aspects of the present disclosure.

FIGS. 5 through 7 show block diagrams of a device that supports enablinga network-trigger change of network slices, in accordance with one ormore aspects of the present disclosure.

FIG. 8 illustrates a block diagram of a system including a networkentity that supports enabling a network-trigger change of networkslices, in accordance with one or more aspects of the presentdisclosure.

FIGS. 9 through 11 show block diagrams of a device that supportsenabling a network-trigger change of network slices, in accordance withone or more aspects of the present disclosure.

FIG. 12 illustrates a block diagram of a system including a UE thatsupports enabling a network-trigger change of network slices, inaccordance with one or more aspects of the present disclosure.

FIGS. 13 through 20 illustrate methods for enabling a network-triggerchange of network slices, in accordance with one or more aspects of thepresent disclosure.

DETAILED DESCRIPTION

The described features generally relate to methods, systems, and devicesfor wireless communication that supports enabling a network-triggerchange of network slices. A UE may establish a protocol data unit (PDU)session for a logical data network. The logical data network may also bereferred to as a network slice. In some cases, a UE may select a networkslice based on an application or subscription service. For example, a UEmay have an application that is an internet protocol (IP) multimediasystems (IMS) voice application, the UE may select a network slice thatis configured to support this mobile broadband application. A UE may,additionally or alternatively, have an application that is configured asan Internet of Everything (IoT) application; for example, the IoTapplication may configure the UE to operate as an IoT gateway devicethat compiles and transmits data to a remote server, periodically. Assuch, the UE may select a network slice that is configured to supportmassive IoT data traffic. By having different network slices servingdifferent applications or subscriptions, etc. the UE may improve itsresource utilization in a network, while also satisfying performancerequirements of individual applications of the UE.

The network slices of the UE may be served by an access and mobilitymanagement function (AMF). In addition, session management of thenetwork slices may be performed by a session management function (SMF).The network may determine a change in a set of allowed network slicesfor a UE. This change may be identified; for example, by comparingprevious allowed network slices to new-allowed network slices. Theprevious allowed network slices may include a set of network slicesallowed for a UE, before the network determines a change in the set ofallowed network slices. In addition, the new-allowed network slices mayinclude a set of network slices allowed for the UE, after the networkdetermines a change in the set of allowed network slices. The networkmay, in some cases, provide network slice selection assistanceinformation (NSSAI) or a set of allowed NSSAIs (S-NSSAI) to the UE. TheNSSAI may include information indicating allowed or supported networkslices for the UE to use, among other information.

The network may change a set of network slices for a UE. For example, inthe case that that a new network slice is identified in the set ofnew-allowed network slices, a current AMF serving the UE may determine alack of capabilities to service the new network slice. As a result, anAMF that can service the new network slice may be identified. In otherwords, a change in a set of allowed network slices may involve a changein a serving AMF. In one aspect, a current AMF may reach out to a newAMF. The new AMF may not serve isolated network slices. In anotheraspect, the new-allowed network slices may be isolated. In other words,the current AMF serving the new-allowed network slices may require a newAMF that is not accessible by other AMFs. In some examples, the networkmay change a set of network slices that the UE is using, while the UE isin an RM-REGISTERED state.

In the RM-REGISTERED state, the UE may already be registered with an AMFfor one or more network slices. The UE may indicate the one or morenetwork slices in an initial NSSAI request during an initialregistration procedure with the AMF. In the case the network changes theset of network slices, the network may transmit a new NSSAI to the UE.The UE may receive the new NSSAI. The UE may re-register with arequested NSSAI including the current S-NSSAI the UE is registered withand a new S-NSSAI. Because of the new requested NSSAI, if the networkdetermines that a different AMF (i.e., not the current AMF) is requiredto serve the UE, the network may identify and select a new AMF.

In some cases, the UE performs a de-registration procedure. The networkmay disallow a direct transfer between a serving AMF and a new targetAMF because the new AMF is associated with a different registration areaor is isolated. In this case, session and service continuity may not beconsidered, where the de-registration procedure is suitable. However,existing de-registration procedures may not provide sufficientinformation for the UE to act accordingly. Alternatively, a network mayutilize generic UE configuration update procedure to update a set ofNSSAI that the UE is allowed to use, by providing a new set of NSSAI inthe UE configuration update request message. However, in some cases theUE may not be required to perform a re-registration due to the change ofNSSAI (e.g. a new network slice may be available and the UE requiresconnectivity to it, or applications that were using a network slice mayno longer be available on PDU sessions of another network slice to whichthe UE is not registered). As a result, the UE may acknowledge theupdate of allowed NSSAI with a UE configuration update complete message.If the UE requests additional S-NSSAI other than received values (e.g.S-NSSAI in the configured NSSAI that was not requested previously), thenthe UE may initiate a registration procedure. The network may thenconfirm with the registration accept message. However, simply notifyingthe UE may not be sufficient in terms of usage of temporary ID (e.g., 5GGUTI) and NSSAI requests.

As such, existing solutions do not support relocation of a serving AMFfor a UE when the current AMF can reach a target AMF (i.e., the targetAMF does not serve isolated slices) or when the new-allowed networkslices are isolated (i.e., the AMF serving the new network slice(s)requires a separate AMF not reachable by other AMFs). The presentdisclosure provides techniques for AMF relocation based onnetwork-triggering changes of network slices. According to onetechnique, a current AMF may identify a request to change acurrent-allowed NSSAI for a UE. The current AMF may identify a requestto modify the current-allowed NSSAI based on a policy control function(PCF) indication or an indication designating a change in a subscriptionof a network slice. In some examples, the request may include anew-allowed NSSAI.

The current AMF may select a new AMF based on the new-allowed NSSAI. Ifa new AMF can be selected and reached by the current AMF, the currentAMF may determine whether the UE has an active NSI of S-NSSAI associatedwith the current-allowed NSSAIs or an active NSI that is absent in thenew-allowed NSSAI, or both. The current AMF may generate a UE contextand transmit the UE context to the new AMF. The UE context may include aUE PDU status for all existing UE PDU sessions for each active networkslice, associated with the new-allowed NSSAI. As such, thenetwork-triggering change of network slices results in the current AMFtriggering the AMF relocation (i.e., a change from a current AMF to anew AMF).

The current AMF may transmit an AMF relocation request to a new AMF. TheAMF relocation request may include a new-allowed NSSAI or UE context, orboth. Additionally, the current AMF may trigger a PDU release procedurefor each active UE PDU session that is not supported in the new-allowedNSSAI. The new AMF may receive the relocation request from the currentAMF (i.e., now previous AMF). Based on the relocation request, the newAMF may transmit an indication, to one or more SMFs associated with anactive UE PDU session, identifying the change to the AMF. In someexamples, the UE may have a plurality of active UE PDU sessions. The newAMF may determine and allocate a NR (e.g., or other 5G networkidentifier) GUTI for the UE. The UE may receive the NR GUTI from the newAMF in a message; for example, in a UE configuration request message.The message may also include a status provided by the previous AMF orthe new-allowed NSSAI, or both. The status may indicate UE PDU sessionsfor each active network slice. In some examples, the status may indicatea plurality of UE PDU sessions for a plurality of active network slices.Upon receiving the message from the new AMF, the UE may store thenew-allowed NSSAI, the new NR GUTI and release the active UE PDUsessions that are absent in the UE PDU session status.

In some cases, the UE may determine that an additional network slice isrequired in addition to the network slices included in the new-allowedNSSAI that were absent in the previous allowed NSSAI. The UE mayre-register with the network based on the determination that additionalnetwork slices are required. For example, in the previous allowed NSSAI,the UE may have been assigned network slices 0-3; however, in thenew-allowed NSSAI, the UE may be assigned network slices 1, 2, and 4. Assuch, the UE may determine that network slice 4 needs to be registered.As part of re-registering with the network, the UE may transmit an NSSAIrequest. The NSSAI request may include the additional network slice inaddition to the currently registered network slices.

According to a second technique, a de-registration procedure may betriggered by the network. In this case, the current AMF may identify arequest to change one or more network slices associated with acurrent-allowed NSSAI. In response to identifying the request, thecurrent AMF may select a new AMF to serve the network slices associatedwith the new-allowed NSSAI. However, the current AMF may determine thatthe new AMF is not accessible. As a result, the current AMF may transmita de-registration request to the UE. The de-registration request mayinclude an indication to perform a re-registration procedure.Additionally, the de-registration request may include the new-allowedNSSAI or a cause code indicating a new registration request for a set ofnetwork slices due to an AMF change, or both.

In some cases, the current AMF may refrain from releasing an N2signaling connection, until a request to release the connection isreceived from the network (e.g. RAN). In the case that the current AMFreceives the request from the network, the current AMF may trigger a PDUrelease procedure. This procedure may include that for each active UEPDU session that is not supported in the new-allowed NSSAI, that the UEPDU session be released. When all UE PDU sessions are released, the AMFmay also release the UE context.

The UE may receive the de-registration request from the current AMF. Insome cases, the UE may determine that the de-registration requestincludes a re-registration request; for example, the re-registrationrequest may be identified in a cause code indicating a new registrationrequest for a new network slice based on an AMF change. The UE maydetermine an allowed NSSAI based on the de-registration request, andstore the allowed NSSAI locally or remotely, or both. In some cases, theUE may determine which network slices in the new-allowed NSSAI toconnect to in order to create a NSSAI request.

Additionally or alternatively, the UE may analyze the cause code toexecute additional operations. The UE may, for example, remove a currentGUTI (e.g., 5G GUTI) based on the cause code. In some cases, an upperlayer (e.g., NAS layer) of the UE may indicate to a lower layer (e.g.,AS layer) to release a signaling connection or to reestablish asignaling connection with the network, or both based on the cause code.The UE may transmit a request to reestablish a signaling connectionincluding the NSSAI request, to the network.

In some examples, the signaling connection may be an RRC connection. Inthis case, the UE may perform an RRC connection release or an RRCconnection establishment procedure, or both. The network may receive thesignaling indication associated with the RRC connection release or RRCconnection establishment procedure. The signaling indication may includean NSSAI request. The NSSAI request may contain indication of requestednetwork slices based on the NSSAI. According to one technique, thenetwork may determine a change in NSSAI for a UE. The network may modifythe current-allowed NSSAI based on a PCF indication or an indicationdesignating a change in a subscription of a network slice. In someexamples, the modification may include identifying new-allowed networkslices supported for the UE, alone or in addition to the network slicesof the NSSAI request. The network may select a new AMF to serve thenetwork slices associated with the new-allowed NSSAI and initiate an AMFrelocation for the signaling connection of the RRC connection release orRRC connection establishment. In other words, a change in a set ofallowed network slices may involve a change in a serving AMF for RRCconnectivity. In one aspect, a current AMF may reach out to a new AMF.Communication between the current AMF and the new AMF may be redirectedvia the network or established via a direct connection between the AMFs.Alternatively, the signaling connection may be a Nwu connection; forexample, an IPSec tunnel connection. In this case, the UE may release orreestablish the IPSec tunnel connection, or both.

In some cases, an upper layer (e.g., NAS layer) of the UE may indicateto a lower layer (e.g., AS layer) to modify a signaling connection withthe network based on the cause code. In this case, the UE may transmit amessage (e.g., new RRC reconfiguration request message or Nwu signaling)to the network to modify a signaling connection. In some cases, the RRCreconfiguration message or the Nwu signaling may include the NSSAIrequest, or a signaling path reconfiguration indicated by the causecode, or a current GUTI (e.g., 5G GUTI), or a combination thereof to thenetwork. Additionally, the UE may include a NAS message including theNSSAI request in the RRC reconfiguration message. In some cases, themessage transmitted to the network by the UE may be an IKEv2INFORMATIONAL message. This message may be identified by an exchangetype value set to a predetermined number (e.g., 37), or a newreconfiguration signaling connection message identified by an exchangetype value set between a predetermined range (e.g., a value between 240and 255) that may be reserved for private use. In some examples, theNSSAI request, the cause code indicating a signaling pathreconfiguration, or the GUTI, or a combination thereof may be includedin a generic payload with a payload type set to a predetermined number(e.g., 43) to indicate a vendor ID payload.

The network may receive the RRC reconfiguration request message from theUE. At this point, the network may select a serving AMF based on theNSSAI request included in the RRC reconfiguration request message.According to one technique, the network may evaluate considerations ofthe current-allowed network slices associated with the NSSAI request. Insome cases, network may determine a change in NSSAI for the UE. Thenetwork may modify the current-allowed NSSAI based on a PCF indicationor an indication designating a change in a subscription of a networkslice. In some examples, the modification may include identifyingnew-allowed network slices supported for the UE, alone or in addition tothe network slices of the NSSAI request. The network may select a newAMF to serve the network slices associated with the new-allowed NSSAIand initiate an AMF relocation. In other words, a change in a set ofallowed network slices may involve a change in a serving AMF. In oneaspect, a current AMF may reach out to a new AMF. The network mayestablish an N2 signaling connection with the serving AMF and transmitthe NAS message received from the UE. Additionally or alternatively, thenetwork may transmit a request, to release an N2 signaling connection,to a previous AMF. Once the network registers with the serving AMF, thenetwork may receive from the serving AMF a new GUTI for the UE. As aresult, the network may transmit the new GUTI to the UE. In someexamples, the network may transmit same message as the UE. For example,the network may transmit the new GUTI in a generic payload with apayload type associated with a vendor ID payload.

Aspects of the disclosure are initially described in the context of awireless communications system. Exemplary UEs, base stations (e.g., eNB,gNB), systems, and process flow for AMF relocation based onnetwork-triggering changes of network slices are then described. Aspectsof the disclosure are further illustrated by and described withreference to apparatus diagrams, system diagrams, and flowcharts thatrelate to enabling a network-trigger change of network slices.

FIG. 1 illustrates an example of a wireless communications system 100that supports enabling a network-trigger change of network slices, inaccordance with one or more aspects of the present disclosure. Thewireless communications system 100 includes base stations 105 (e.g.,gNodeBs (gNBs), and/or radio heads (RHs)), UEs 115, and a core network130. In some examples, the wireless communications system 100 may be aLong Term Evolution (LTE), LTE-Advanced (LTE-A) network, or a NRnetwork. In some cases, wireless communications system 100 may supportenhanced broadband communications, ultra-reliable (i.e., missioncritical) communications, low latency communications, and communicationswith low-cost and low-complexity devices.

UE 115 may establish multiple PDU sessions for multiple network slices.In some cases, UE 115 may select a network slice based on an applicationor subscription service. By having different network slices servingdifferent applications or subscriptions, etc. UE 115 may improve itsresource utilization in wireless communications system 100, while alsosustaining performance requirements of individual applications of the UE115. In some cases, the network slices used by UE 115 may be served byan AMF associated with base station 105 or core network 130, or both. Inaddition, session management of the network slices may be performed by aSMF.

In some cases, a network (e.g., RAN) may determine a change in a set ofallowed network slices for a UE 115. This change may be determined, forexample, by comparing previous allowed network slices to new-allowednetwork slices. An AMF may, in some cases, provide NSSAI or a S-NSSAI toUE 115. The NSSAI may include information indicating allowed networkslices for the UE 115 to use, among other information. The AMF may, insome cases, change a set of network slices for UE 115. For example, inthe case that that a new network slice is identified in the set ofnew-allowed network slices, a serving AMF of UE 115 may determine thatthe serving AMF does not have capabilities to service the new networkslice. As a result, an AMF that can service the new network slice may beidentified. In other words, a change in a set of allowed network slicesmay involve a change in a serving AMF.

In the case a network changes the set of network slices, a serving AMFmay transmit a new set of NSSAIs to UE 115. UE 115 may receive the newset of NSSAIs. In some cases, UE 115 may identify that the new set ofNSSAIs includes a new S-NSSAIs to which the UE 115 may need to connect.UE 115 may re-register with a requested NSSAI including the currentS-NSSAIs the UE 115 is registered with and one or more of the newS-NSSAIs. Because of the new requested NSSAI, if the serving AMFdetermines that a different AMF is required for the UE 115, the servingAMF may identify and select a new AMF. As a result, the wirelesscommunications system 100 is capable of supporting network-triggeredchanges to network slices.

Base stations 105 may wirelessly communicate with UEs 115 via one ormore base station antennas. Each base station 105 may providecommunication coverage for a respective geographic coverage area 110.Communication links 125 shown in wireless communications system 100 mayinclude uplink (UL) transmissions from a UE 115 to a base station 105,or downlink (DL) transmissions, from a base station 105 to a UE 115.Control information and data may be multiplexed on an uplink channel ordownlink according to various techniques. Control information and datamay be multiplexed on a downlink channel, for example, using timedivision multiplexing (TDM) techniques, frequency division multiplexing(FDM) techniques, or hybrid TDM-FDM techniques. In some examples, thecontrol information transmitted during a transmission time interval(TTI) of a downlink channel may be distributed between different controlregions in a cascaded manner (e.g., between a common control region andone or more UE-specific control regions).

UEs 115 may be dispersed throughout the wireless communications system100, and each UE 115 may be stationary or mobile. A UE 115 may also bereferred to as a mobile station, a subscriber station, a mobile unit, asubscriber unit, a wireless unit, a remote unit, a mobile device, awireless device, a wireless communications device, a remote device, amobile subscriber station, an access terminal, a mobile terminal, awireless terminal, a remote terminal, a handset, a user agent, a mobileclient, a client, or some other suitable terminology. A UE 115 may alsobe a cellular phone, a personal digital assistant (PDA), a wirelessmodem, a wireless communication device, a handheld device, a tabletcomputer, a laptop computer, a cordless phone, a personal electronicdevice, a handheld device, a personal computer, a wireless local loop(WLL) station, an Internet of Things (IoT) device, an IoE device, amachine type communication (MTC) device, an appliance, an automobile, orthe like.

In some cases, a UE 115 may also be able to communicate directly withother UEs (e.g., using a peer-to-peer (P2P) or device-to-device (D2D)protocol). One or more of a group of UEs 115 utilizing D2Dcommunications may be within the geographic coverage area 110 of a cell.Other UEs 115 in such a group may be outside the geographic coveragearea 110 of a cell, or otherwise unable to receive transmissions from abase station 105. In some cases, groups of UEs 115 communicating via D2Dcommunications may utilize a one-to-many (1:M) system in which each UE115 transmits to every other UE 115 in the group. In some cases, a basestation 105 facilitates the scheduling of resources for D2Dcommunications. In other cases, D2D communications are carried outindependent of a base station 105.

Some UEs 115, such as MTC or IoT devices, may be low cost or lowcomplexity devices, and may provide for automated communication betweenmachines, i.e., Machine-to-Machine (M2M) communication. M2M or MTC mayrefer to data communication technologies that allow devices tocommunicate with one another or a base station without humanintervention. For example, M2M or MTC may refer to communications fromdevices that integrate sensors or meters to measure or captureinformation and relay that information to a central server orapplication program that can make use of the information or present theinformation to humans interacting with the program or application. SomeUEs 115 may be designed to collect information or enable automatedbehavior of machines. Examples of applications for MTC devices includesmart metering, inventory monitoring, water level monitoring, equipmentmonitoring, healthcare monitoring, wildlife monitoring, weather andgeological event monitoring, fleet management and tracking, remotesecurity sensing, physical access control, and transaction-basedbusiness charging.

Base stations 105 may communicate with the core network 130 and with oneanother. For example, base stations 105 may interface with the corenetwork 130 through backhaul links 132 (e.g., S1, etc.). Base stations105 may communicate with one another over backhaul links 134 (e.g., X2,etc.) either directly or indirectly (e.g., through core network 130). AUE 115 may communicate with the core network 130 through communicationlink 135. Base stations 105 may perform radio configuration andscheduling for communication with UEs 115, or may operate under thecontrol of a base station controller (not shown). In some examples, basestations 105 may be macro cells, small cells, hot spots, or the like.Base stations 105 may also be referred to as evolved NodeBs (eNBs) 105.

A base station 105 may be connected by an S1 interface to the corenetwork 130. The core network may be an evolved packet core (EPC), whichmay include at least one mobility management entity (MME), at least oneserving gateway (S-GW), and at least one Packet Data Network (PDN)gateway (P-GW). The MME may be the control node that processes thesignaling between the UE 115 and the EPC. All user IP packets may betransferred through the S-GW, which itself may be connected to the P-GW.The P-GW may provide IP address allocation as well as other functions.The P-GW may be connected to the network operators IP services. Theoperators IP services may include the Internet, the Intranet, an IPMultimedia Subsystem (IMS), and a Packet-Switched (PS) StreamingService.

The core network 130 may provide user authentication, accessauthorization, tracking, IP connectivity, and other access, routing, ormobility functions. At least some of the base stations 105 (e.g.,eNodeBs (eNBs, network access devices, gNBs) 105-a, gNBs, or access nodecontrollers (ANCs) may interface with the core network 130 throughbackhaul links 132 (e.g., S1, S2, etc.) and may perform radioconfiguration and scheduling for communication with the UEs 115. In someconfigurations, various functions of each access network entity or basestation 105 may be distributed across various network devices (e.g.,radio heads and access network controllers) or consolidated into asingle network device (e.g., a base station 105).

One or more of network devices 105 may include a network slice manager101, which may receive a network-trigger; determine to modifycurrent-allowed network slice associated with a current-allowed NSSAIused by the UE 115 based on the received network-trigger; identifynew-allowed NSSAI for the UE 115 based on the determining; and select atarget AMF based on the new-allowed NSSAI, where the target AMF isaccessible by the source AMF. The network slice manager 101 mayalternatively, receive an AMF relocation request for UE 115 currentlyserved by a source AMF, the AMF relocation request may include anew-allowed NSSAI and UE context information. The network slice manager101 may allocate an updated NR GUTI for the UE 115 based on the AMFrelocation request; and transmit to the UE 115 a configuration requestmessage including the updated NR GUTI, an updated status of an existingUE PDU session, or the new-allowed NSSAI, or a combination thereof.

In some cases, network slice manager 101 may receive a network-triggerfrom a UE 115 served by a source AMF; determine to modifycurrent-allowed NSSAI associated with a current-allowed S-NSSAI used bythe UE 115 based on the received network-trigger; identify new-allowedNSSAI for the UE 115; and determine that a target AMF associated withthe new-allowed NSSAI is inaccessible by the source AMF. Alternatively,in some cases, network slice manager 101 may receive from UE 115 a RRCconnection request including NSSAI; select a target AMF to serve UE 115based on the NSSAI; establish an N2 signaling connection with theselected AMF; and transmit NAS message received from the UE 115 to theselected AMF using the N2 signaling connection.

UEs 115 may include a network slice manager 102, which may receive, froma network device 105, a configuration message indicating a request toregister one or more new network slices associated with a new-allowednetwork slice, a NR GUTI associated with a target AMF, a status of anexisting active UE PDU session of the UE 115, or new-allowed NSSAI, or acombination thereof; store the new-allowed NSSAI and NR GUTI; identifyan active UE PDU session based on the status of existing active UE PDUsession information included in the configuration message, theidentified active UE PDU session is unsupported in the new-allowedNSSAI; and release the identified active UE PDU session. Additionally oralternatively, the network slice manager 101 may identify are-registration request and a code indicating a request to register aset of network slices associated with a new-allowed NSSAI based on areceived de-registration request from a AMF that is serving the UE 115;identify the new-allowed NSSAI based on the received de-registrationrequest; and generate an NSSAI request for registering the set ofnetwork slices based on the code.

In some examples, establishing a user plane connection to a data networkvia one or more network slice instances may include performing aresource management procedure to select an AMF that supports the one ormore network slices. Additionally or alternatively, the managementprocedure may include establishing a PDU session to the data network viathe network slice instance. UE 115 may register with a network (e.g.,PLMN, LTE, NR). When UE 115 registers with the network, UE 115 maydetermine a configured NSSAI or an allowed NSSAI. UE 115 may provide tothe network using RRC and NAS layer a NSSAI request based on determininga configured NSSAI or an allowed NSSAI. The NSSAI request may includeS-NSSAI associated with the network slice to which UE 115 is requestingto register. In addition, the NSSAI request may include a temporaryidentifier (e.g., GUTI) assigned to UE 115.

The NSSAI request may include a configured NSSAI or a subset of theconfigured NSSAI, in the case that the UE 115 has an no allowed NSSAI orno allowed NSSAI. In some cases, the NSSAI request may include theallowed NSSAI, or a subset of the allowed NSSAI, one or more S-NSSAIsassociated with the configured NSSAI for which no corresponding S-NSSAIis supported in the allowed NSSAI, and that were not previouslysupported by the network. The subset of allowed NSSAI may include anS-NSSAI associated the previous allowed NSSAI for the network, in someexamples.

UE 115 may provide in the NSSAI request an S-NSSAI from the configuredNSSAI that the UE 115 previously provided to the network in a currentregistration area. The NSSAI request may also be included in an RRCconnection establishment message or in NAS message, or both. The network(e.g., RAN) may route NAS signaling between UE 115 and an AMF selectedusing the requested NSSAI obtained during an RRC connectionestablishment. If the network (e.g., RAN) is unable to select an AMFbased on the requested NSSAI, the network may route the NAS signaling toan AMF from a set of default AMFs.

In some cases, upon registration, the UE 115 may be provided with atemporary identifier by a serving AMF. The temporary identifier may beincluded in one or more RRC connection establishment message duringsubsequent initial accesses to enable the network (e.g., RAN) to routethe NAS signaling between the UE 115 and an appropriate AMF. The networkmay also return a new-allowed NSSAI identifying network slicespermitted. The UE 115 may store the new-allowed NSSAI and override anypreviously stored allowed NSSAI for the network.

The network may also discard an S-NSSAI provided by UE 115 in arequested NSSAI with a discard cause code. In some examples, the networkmay transmit an indication identifying whether the discarded S-NSSAI ispermanent (e.g. the S-NSSAI may not be supported by the network in atleast the current registration area) or temporary (e.g. the networkslice associated with the S-NSSAI may be temporarily unavailable). Insome cases, when receiving from UE 115 a NSSAI request and a temporaryidentifier in an RRC message, if the network (e.g., RAN) determinescapability to reach an AMF associated with the temporary identifier, thenetwork may forward the request to the AMF. Alternatively, the networkmay select a suitable AMF based on the NSSAI request provided by the UE115, and forward the request to the selected AMF. In some cases, if thenetwork is unable to select an AMF based on the NSSAI request, then therequest may be sent to a default AMF.

In some cases, when UE 115 registers with a network, if the UE has noconfigured NSSAI or allowed NSSAI, the network (e.g., RAN) may routesome or all NAS signaling from and to UE 115 to a default AMF. UE 115may also transmit an indication of an NSSAI in a RRC connectionestablishment or initial NAS message; unless, UE 115 has a configuredNSSAI or allowed NSSAI for a corresponding network. In some cases, uponregistration, UE 115 may receive a temporary identifier by an AMF. Inaddition, UE 115 may receive an allowed NSSAI identifying network slicespermitted by the network for the UE 115. The network slices may part ofthe subscribed default S-NSSAI of the UE 115. The UE 115 may alsoinclude the temporary identifier in a RRC connection establishmentmessage during subsequent initial accesses to enable the network toroute NAS signaling between the UE 115 and an appropriate AMF.

In some examples, wireless communications system 100 may providemodification to a network slice for UE 115. In addition, wirelesscommunications system 100 may provide modification to a set of networkslices for UE 115. A set of network slices for UE 115 may change duringone more time instances during and following registration with anetwork. In addition, a change to the set of network slices may beinitiated by the network, or UE 115 based on one or more conditions. Thenetwork may change a set of network slices to which UE 115 is registeredbased on local policies; for example, subscription changes or UEmobility, or both.

In some cases, the network may trigger change to the set of networkslices during a registration procedure. For example, an access node (AN)of the network may receive from UE 115 a RRC connection requestincluding NSSAI; and determine a change in network slice considerationsof the current-allowed NSSAI used by a source AMF of the registrationprocedure. The AN may determine to modify current-allowed NSSAI based ona network trigger of the local policies; and identify a new-allowedNSSAI including new-allowed network slices supported for the UE 115. Inother cases, an of the network may receive a UE initiated request forrelocation from a source AMF associated with a set of current-allowednetwork slices of a network connection. The AN may determine a change innetwork slice consideration of the current-allowed NSSAI used by thesource AMF; and determine to modify current-allowed NSSAI based on localpolicies of the network and the relocation request.

The network may also select a new AMF based on the new-allowed NSSAI. Insome cases, the network may determine that a redirection between acurrent AMF and the new selected AMF is possible. As a result, thenetwork may trigger an AMF relocation towards the new AMF and thecurrent AMF may transmit the new-allowed NSSAI to the new selected AMF.The current AMF may also trigger the release of PDU sessions for aS-NSSAI that are not supported by the new-allowed NSSAI. The current AMFmay communicate with the new AMF according to redirection by the networkor direct signaling between AMFs. Alternatively, the network maydetermine that relocation to a new AMF that supports the new-allowedNSSAI is not possible. As a result, the current AMF may transmit thenew-allowed NSSAI to the UE 115 using a network-initiatedde-registration procedure. The de-registration procedure may include anindication for the UE 115 to initiate a registration procedure with theupdated and new S-NSSAI, and that the cause of the re-registration isdue to the change of the supported network slices. As a result, the UE115 may initiate a registration procedure including a NSSAI requestbased on the new-allowed NSSAI, an refrain from providing the currenttemporary identifier of UE 115.

A data network may be associated with an S-NSSAI. In some cases, anetwork operator may provide to UE 115 network slice selection policy(NSSP). The NSSP may include one or more NSSP rules, each oneassociating an application with a certain S-NSSAI. In some cases, adefault rule may match all applications to a S-NSSAI. In some cases, aUE 115 application associated with a S-NSSAI may request datatransmission. If UE 115 has one or more PDU sessions established andassociated with the S-NSSAI, UE 115 may route the user data of thisapplication in one of these PDU sessions, unless other conditions in theUE 115 disallow the use of these PDU sessions. In addition, if the UE115 application provides a DNN, UE 115 may determine which PDU sessionto use. In some cases, if UE 115 does not have a PDU session establishedand associated with the S-NSSAI, UE 115 may request a new PDU sessionassociated with the S-NSSAI and with a DNN that may be provided by theapplication. In order for the network to select a proper resource forsupporting network slicing in the RAN, RAN needs to be aware of thenetwork slices used by the UE 115. An AMF may select an SMF in a networkslice instance based on S-NSSAI, DNN and other information; for example,UE subscription and local operator policies, when the UE triggers theestablishment of a PDU session. The selected SMF establishes a PDUsession based on S-NSSAI and DNN.

Wireless communications system 100 may operate in an ultra-highfrequency (UHF) frequency region using frequency bands from 700 MHz to2600 MHz (2.6 GHz), although some networks (e.g., a wireless local areanetwork (WLAN)) may use frequencies as high as 4 GHz. This region mayalso be known as the decimeter band, since the wavelengths range fromapproximately one decimeter to one meter in length. UHF waves maypropagate mainly by line of sight, and may be blocked by buildings andenvironmental features. However, the waves may penetrate wallssufficiently to provide service to UEs 115 located indoors. Transmissionof UHF waves is characterized by smaller antennas and shorter range(e.g., less than 100 km) compared to transmission using the smallerfrequencies (and longer waves) of the high frequency (HF) or very highfrequency (VHF) portion of the spectrum. In some cases, wirelesscommunications system 100 may also utilize extremely high frequency(EHF) portions of the spectrum (e.g., from 30 GHz to 300 GHz). Thisregion may also be known as the millimeter band, since the wavelengthsrange from approximately one millimeter to one centimeter in length.Thus, EHF antennas may be even smaller and more closely spaced than UHFantennas. In some cases, this may facilitate use of antenna arrayswithin a UE 115 (e.g., for directional beamforming). However, EHFtransmissions may be subject to even greater atmospheric attenuation andshorter range than UHF transmissions.

Thus, wireless communications system 100 may support millimeter wave(mmW) communications between UEs 115 and base stations 105. Devicesoperating in mmW or EHF bands may have multiple antennas to allowbeamforming. That is, a base station 105 may use multiple antennas orantenna arrays to conduct beamforming operations for directionalcommunications with a UE 115. Beamforming (which may also be referred toas spatial filtering or directional transmission) is a signal processingtechnique that may be used at a transmitter (e.g., a base station 105)to shape and/or steer an overall antenna beam in the direction of atarget receiver (e.g., a UE 115). This may be achieved by combiningelements in an antenna array in such a way that transmitted signals atparticular angles experience constructive interference while othersexperience destructive interference.

Multiple-input multiple-output (MIMO) wireless systems use atransmission scheme between a transmitter (e.g., a base station 105) anda receiver (e.g., a UE 115), where both transmitter and receiver areequipped with multiple antennas. Some portions of wirelesscommunications system 100 may use beamforming. For example, base station105 may have an antenna array with a number of rows and columns ofantenna ports that the base station 105 may use for beamforming in itscommunication with UE 115. Signals may be transmitted multiple times indifferent directions (e.g., each transmission may be beamformeddifferently). A mmW receiver (e.g., a UE 115) may try multiple beams(e.g., antenna subarrays) while receiving the synchronization signals.

In some cases, the antennas of a base station 105 or UE 115 may belocated within one or more antenna arrays, which may support beamformingor MIMO operation. One or more base station antennas or antenna arraysmay be collocated at an antenna assembly, such as an antenna tower. Insome cases, antennas or antenna arrays associated with a base station105 may be located in diverse geographic locations. A base station 105may multiple use antennas or antenna arrays to conduct beamformingoperations for directional communications with a UE 115.

In some cases, wireless communications system 100 may be a packet-basednetwork that operate according to a layered protocol stack. In the userplane, communications at the bearer or Packet Data Convergence Protocol(PDCP) layer may be IP-based. A Radio Link Control (RLC) layer may insome cases perform packet segmentation and reassembly to communicateover logical channels. A Medium Access Control (MAC) layer may performpriority handling and multiplexing of logical channels into transportchannels. The MAC layer may also use Hybrid ARQ (HARQ) to provideretransmission at the MAC layer to improve link efficiency. In thecontrol plane, the Radio Resource Control (RRC) protocol layer mayprovide establishment, configuration, and maintenance of an RRCconnection between a UE 115 and a network device 105-c, network device105-b, or core network 130 supporting radio bearers for user plane data.At the Physical (PHY) layer, transport channels may be mapped tophysical channels.

Wireless communications system 100 may support operation on multiplecells or carriers, a feature which may be referred to as carrieraggregation (CA) or multi-carrier operation. A carrier may also bereferred to as a component carrier (CC), a layer, a channel, etc. Theterms “carrier,” “component carrier,” “cell,” and “channel” may be usedinterchangeably herein. A UE 115 may be configured with multipledownlink CCs and one or more uplink CCs for carrier aggregation. Carrieraggregation may be used with both FDD and TDD component carriers.

In some cases, wireless communications system 100 may utilize enhancedcomponent carriers (eCCs). An eCC may be characterized by one or morefeatures including: wider bandwidth, shorter symbol duration, shorterTTIs, and modified control channel configuration. In some cases, an eCCmay be associated with a carrier aggregation configuration or a dualconnectivity configuration (e.g., when multiple serving cells have asuboptimal or non-ideal backhaul link). An eCC may also be configuredfor use in unlicensed spectrum or shared spectrum (where more than oneoperator is allowed to use the spectrum). An eCC characterized by widebandwidth may include one or more segments that may be utilized by UEs115 that are not capable of monitoring the whole bandwidth or prefer touse a limited bandwidth (e.g., to conserve power).

A shared radio frequency spectrum band may be utilized in an NR sharedspectrum system. For example, an NR shared spectrum may utilize anycombination of licensed, shared, and unlicensed spectrums, among others.The flexibility of eCC symbol duration and subcarrier spacing may allowfor the use of eCC across multiple spectrums. In some examples, NRshared spectrum may increase spectrum utilization and spectralefficiency, specifically through dynamic vertical (e.g., acrossfrequency) and horizontal (e.g., across time) sharing of resources.

In some cases, wireless communications system 100 may utilize bothlicensed and unlicensed radio frequency spectrum bands. For example,wireless communications system 100 may employ LTE License AssistedAccess (LTE-LAA) or LTE Unlicensed (LTE U) radio access technology or NRtechnology in an unlicensed band such as the 5 Ghz Industrial,Scientific, and Medical (ISM) band. When operating in unlicensed radiofrequency spectrum bands, wireless devices such as base stations 105 andUEs 115 may employ listen-before-talk (LBT) procedures to ensure thechannel is clear before transmitting data. In some cases, operations inunlicensed bands may be based on a CA configuration in conjunction withCCs operating in a licensed band. Operations in unlicensed spectrum mayinclude downlink transmissions, uplink transmissions, or both. Duplexingin unlicensed spectrum may be based on frequency division duplexing(FDD), time division duplexing (TDD) or a combination of both.

FIG. 2 illustrates a wireless communications system 200 that supportsenabling a network-trigger change of network slices in accordance withone or more aspects of the present disclosure. In some examples,wireless communications system 200 may implement aspects of wirelesscommunications system 100. Wireless communications system 200 maysupport network slicing. In some cases, access to network slicing may bebased on a subscription and network deployment options; for example,some AMFs may not support all network slices requested by a UE. Inaddition, there may be isolated AMFs for some network slice(s) that donot support other network slices, and may be reached by other AMFs thatsupport the same network slice. Wireless communications system 200 mayperform de-registration with re-registration for isolated networkslices, and assign parameters in order to enable a selection of anappropriate AMF. In addition, for non-isolated network slices, an AMFrelocation procedure may be triggered by a current AMF, to the new AMF.

The wireless communications system 200 may include UE 215, that may beexamples of UE 115 as described with reference to FIG. 1. The wirelesscommunications system 200 may also include AMF component 205, AMFcomponent 210, RAN component 220, and SMF component 230. AMF component205, AMF component 210, and AMF component 210 may be located locally orremote from a base station or core network such as base stations 105 orcore network 130, as described with reference to FIG. 1.

UE 215 may establish a session with one or more network slices (notshown). In some examples, the session may include multiple PDU sessionsassociated with multiple network slices. A PDU session may be anassociation between UE 215 and a data network (e.g., AMF component 205or AMF component 210) that provides a PDU connectivity service. In somecases, the association may be an IP, an Ethernet, or unstructured type.The PDU connectivity service may be a service that exchanges PDUsbetween UE 215 and a data network (e.g., RAN component 220).Communication links 260 shown in wireless communications system 200 mayinclude UL transmissions from UE 215 to one or more network entities(e.g., AMF component 205, AMF component 210, RAN component 220, and SMFcomponent 230), or DL transmissions, from one or more of the networkentities (e.g., AMF component 205, AMF component 210, RAN component 220,and SMF component 230) to UE 215.

AMF component 205 may be a current AMF serving network slices used by UE215. These network slices may be associated with a current-allowedNSSAI. NSSAI may include parameters to assist selection of a RAN and acore network for a network slice instance used by UE 215. In some cases,a single NSSAI may be associated with multiple network slices. In somecases, the network may also select a RAN and a core network based on UE215 capabilities and subscription information. Additionally, NSSAI mayinclude a session management NSSAI. The session management NSSAI mayinclude a network slice service type or a network slice identifier (ID),or both. The network slice service type may identify features andservices supported by a network slice.

A network may trigger a change to the current-allowed NSSAI. Forexample, the network may change a parameter associated with a capabilityof a network slice. That is, a network slice may change capabilities forservicing a subscription. In some cases, due to the change of thenetwork slice(s), UE 215 may deregister with a current AMF and registerwith a new AMF. In other cases, due to the change of the networkslice(s), the network may initiate redirection of network connectivitythrough a serving AMF.

According to a first technique, AMF component 205 may trigger AMFrelocation. AMF relocation may include triggering the UE 215 to changeto a new AMF. In some cases, AMF component 205 may receive a new-allowedNSSAI based on a change to the current-allowed NSSAI. For example, AMFcomponent 205 may determine that a current-allowed NSSAI for UE 215 mayrequire modification based on a network trigger including at least a PCFindication or a subscription change. AMF component 205 may determine tomodify a current-allowed network slice used by UE 215 based on thenew-allowed NSSAI. As such, AMF component 205 may modify thecurrent-allowed NSSAI used by UE 215.

AMF component 205 may select a new AMF based on the new-allowed NSSAI.For example, AMF component 205 may select AMF component 210 as the newAMF. In some cases, AMF component 205 may also determine that UE 215 hasan active network slice instance (NSI) associated with an NSSAI of acurrent-allowed S-NSSAI. In some cases, AMF component 205 may determinewhether UE 215 has one or more NSI active for any of the S-NSSAIs thatbelong to the current-allowed NSSAI, and that are not in the new-allowedNSSAI. That is, AMF component 205 may identify that an active NSIsupported in the current-allowed NSSAI associated with UE 215 issupported in the new-allowed NSSAI. AMF component 205 may generate astatus report. In some cases, the status report may be UE context. TheUE context may include a status of all existing UE PDU sessionsassociated with an active NSI. AMF component may transmit the statusreport to AMF component 210.

In some cases, AMF component 205 may trigger AMF relocation due to achange of supported NSSAIs in the received new-allowed NSSAI. AMFcomponent 205 may transmit an AMF relocation request to AMF component210 via communication link 260. The AMF relocation request may includethe new-allowed NSSAI and the status report. In this case, the statusreport may include the UE PDU status of all the UE sessionscorresponding to S-NSSAIs in the new-allowed NSSAI. Additionally oralternatively, the status report may include current NR GUTI. AMFcomponent 205 may trigger a release procedure, in some cases. Therelease procedure may be triggered based on direct signaling to UE 215.The release procedure may be a PDU release procedure for each active PDUsession that is not supported in the new-allowed NSSAI. Similarly, theAMF component 205 may trigger the release procedure to AMF component 210via communication link 260.

According to a second technique, RAN component 220 may determine achange in NSSAI for UE 215 and trigger AMF relocation. RAN component 220may determine a new-allowed NSSAI based on a change to thecurrent-allowed NSSAI. For example, RAN component 220 may determine thata current-allowed NSSAI for UE 215 may require modification based on anetwork trigger including at least a PCF indication or an indicationdesignating a change in a subscription of a network slice. RAN component220 may determine to modify a current-allowed network slice used by UE215 based on the new-allowed NSSAI. As such, RAN component 220 maymodify the current-allowed NSSAI used by UE 215.

RAN component 220 may select a new AMF based on the new-allowed NSSAI.For example, RAN component 220 may select AMF component 210 as the newAMF. RAN component 220 may then trigger AMF relocation due to a changeof supported NSSAIs in the received new-allowed NSSAI. RAN component 220may transmit an AMF relocation request to AMF component 210 viacommunication link 260. The AMF relocation request may include thenew-allowed NSSAI and the status report. In this case, the status reportmay include the UE PDU status of all the UE sessions corresponding toS-NSSAIs in the new-allowed NSSAI. Additionally or alternatively, thestatus report may include a current NR GUTI. AMF component 210 mayreceive the status report and provide a response including an updated NRGUTI for UE 215.

At least one of AMF component 210 and RAN component 220 may transmit anindication identifying a change in AMF (e.g., change from AMF component205 to AMF component 210) for network slices associated with thenew-allowed NSSAI, to SMF component 230. These network slices may beassociated with an active PDU session(s). In some examples, the networkslices may be associated with a same or different SMF component 230. Asa result, AMF component 210 may transmit the indication to multiple SMFcomponents (not shown). In some cases, AMF component 210 may determineand allocate a NR (e.g., or other 5G network identifier) GUTI for UE215. The UE 215 may receive the NR GUTI from AMF component 210 in amessage; for example, in a UE configuration request message viacommunication links 260. The message may also include a UE PDU sessionstatus report (e.g., associated with UE context) provided by AMFcomponent 205 or the new-allowed NSSAI, or both.

The message may, alternatively, be an IKEv2 INFORMATIONAL message. Thismessage may be identified by an exchange type value set to apredetermined number (e.g., 37), or a new reconfiguration signalingconnection message identified by an exchange type value set between apredetermined range (e.g., a value between 240 and 255) that may bereserved for private use. In some examples, the NSSAI request, the causecode indicating a signaling path reconfiguration, or the GUTI, or acombination thereof may be included in a generic payload with a payloadtype set to a predetermined number (e.g., 43) to indicate a vendor IDpayload.

Upon receiving the message from AMF component 210, UE 215 may store thenew-allowed NSSAI, the new NR GUTI and releases active PDU sessions thatare absent in the UE PDU session status report. In some cases, UE 215may determine that a number of additional network slices are required inaddition to the network slices included in the new-allowed NSSAI. Inother words, the number of additional network slices may have not beensupported in the previous allowed NSSAI. UE 215 may re-register with anetwork (e.g., base station) based on determining that additionalnetwork slices are assigned. For example, in the previous allowed NSSAI,UE 215 may have been assigned network slices 1, 2, and 3; however, inthe new-allowed NSSAI, the UE may be assigned network slices 1, 4, and5. As such, the UE may determine that network slices 4 and 5 are newlysupported. As part of re-registering with the network, UE 215 maytransmit an NSSAI request. The NSSAI request may include the additionalnetwork slice(s) (e.g., network slices 4 and 5) and the currentlyregistered network slices. As such, the UE may determine that networkslice 4 needs to be registered. As part of re-registering with thenetwork, the UE may transmit an NSSAI request.

In some examples, during a registration procedure in wirelesscommunications system 200, RAN component 220 may determine that UE 215should be served by a different AMF (e.g., AMF Component 210 instead ofAMF component 205) based on network slices identified in a new-allowedNSSAI. In some cases, AMF component 205 may receive a registrationrequest from RAN component 220. In the case that RAN component 220determines that aspects of the network slices identified in thenew-allowed NSSAI should be served by AMF component 210, RAN component220 may trigger an AMF relocation based in part on the new-allowedNSSAI. RAN component 220 may signal AMF component 205 to redirect theregistration request to AMF component 210. Redirecting the request fromAMF component 205 may include transmitting a redirect message and thetransmission may be via the RAN component 220 or via direct signalingbetween AMF component 205 and AMF component 210 (e.g., via communicationlinks 260). In some cases, the redirect message transmitted by AMFcomponent 205 via the RAN component 220 may include information forselection of a new AMF to serve the UE 215.

According to a second technique, a network may trigger a de-registrationprocedure. In some cases, the second technique may apply when a new setof allowed network slices do not overlap with previous set of allowednetwork slices. Similarly, AMF component 205 may be a current AMFserving network slices used by UE 215. These network slices may beassociated with a current-allowed NSSAI. AMF component 205 may receive anew-allowed NSSAI based on a change to the current-allowed NSSAI. Insome cases, AMF component 205 may determine to modify a current-allowednetwork slice used by UE 215 based on the new-allowed NSSAI. As such,AMF component 205 may modify the current-allowed NSSAI used by UE 215.

AMF component 205 may select a new AMF based on the new-allowed NSSAI.In some cases, AMF component 205 may determine that no new AMF can beselected or that the new AMF is not reachable by AMF component 205. Inthis case, AMF component 205 (i.e., the current AMF) may transmit ade-registration request to UE 215. The de-registration request mayinclude an indication to perform a re-registration procedure, thenew-allowed NSSAI, or a code indicating that the de-registration is inresponse to a change of supported network slices in the new-allowedNSSAI, or a combination thereof.

AMF component 205 may refrain from releasing an N2 signaling connectionuntil AMF component 205 receives a request from RAN component 220. Insome cases, RAN component 220 may transmit a request to AMF component205 to release the N2 signaling connection via communication link 260.In response to receiving the request from RAN component 220, AMFcomponent 205 may trigger a release procedure. The release procedure maybe a PDU release procedure for each active PDU session associated withan S-NSSAI that is unsupported in the new-allowed NSSAI. In someexamples, when all the active PDU sessions are released, AMF component205 may release UE context to AMF component 210.

Returning to the case that AMF component 205 transmits thede-registration request to UE 215, UE 215 may determine that the requestis provided by AMF component 205 and that the request includes a codeindicating that the de-registration request is in response to a changeof supported network slices in the new-allowed NSSAI. Additionally, UE215 may identify the new-allowed NSSAI based on the receivedde-registration request. In some cases, UE 215 may store the new-allowedNSSAI locally or remotely, or both. UE 215 may also determine to whichnetwork slices in the received new-allowed NSSAI to connect. Based ondetermining which network slices to connect to, UE 215 may generate aNSSAI request identifying the network slices. UE 215 may transmit theNSSAI request to AMF component 205 or AMF component 210, or both.

UE 215 may also perform operations based on the received code withde-registration request. UE 215 may remove a current NR GUTI based onthe received code. Additionally or alternatively, an upper layer of UE215 may transmit to a lower layer of the UE 215: an indication torelease a connection with RAN component 220 and to re-establish theconnection, or the NSSAI request, or an indication to refrain fromproviding a NR GUTI, or a combination thereof. In some examples, theupper layer may be a NAS layer and the lower layer be an AS layer. Insome cases, UE 215 may transmit a request to re-establish the connectionbased on the indication to re-establish the connection, where therequest includes the NSSAI request. In some examples, the connection maybe a RRC connection. In this case, UE 215 may perform a RRC connectionrelease procedure or an RRC connection establishment procedure, or bothbased on the indication to release a connection with RAN component 220and to re-establish the connection. Alternatively, the connection may bean IP security (IPsec) tunnel connection. In this case, UE 215 mayperform an IPsec tunnel release procedure or an IPsec tunnelestablishment procedure, or both based on the indication to release aconnection with a RAN and to re-establish the connection.

In some cases, the upper layer of UE 215 may transmit to the lower layerof the UE 215 to modify a connection with RAN component 220, andprovided the NSSAI request. UE 215 may transmit a new RRCreconfiguration request message including the NSSAI request, or a codeindicating signaling path configuration, or a current NR GUTI, or acombination thereof. Alternatively, UE 215 may transmit a Nwu messageincluding the NSSAI request, or the code indicating signaling pathconfiguration, or the current NR GUTI, or a combination thereof. In someexamples, UE 215 may include a NAS registration request message in theRRC message, providing the NSSAI request.

RAN component 220 may receive a RRC request message including the NSSAIrequest from UE 215. According to one technique, RAN component 220 mayselect AMF component 210 as a target AMF to serve UE 215 based on theNSSAI received in the RRC request message. A connection between the RANcomponent 220 and the AMF component 210 may be established based on theselecting the AMF component 210 to serve UE 215. For example, RANcomponent 220 and AMF component 210 may establish a connection viacommunication links 260. In some examples, as part of establishing theconnection with the AMF component 210, RAN component 220 may transmitthe received NAS message from UE 215 to AMF component 210. Additionally,the established connection between AMF component 210 and RAN component220 may be an N2 signaling connection.

According to another technique, RAN component 220 may select AMFcomponent 210 as a target AMF to serve UE 215 based on the NSSAIreceived in the RRC request message, and establish a connection with AMFcomponent 210 via communication links 260. In some cases, RAN component220 may transmit to AMF component 205 (e.g., now previous AMF) a requestto release a connection; for example, an N2 signaling connection betweenAMF component 205 and RAN component 220 or UE 215, or both. In somecases, RAN component 220 may receive, from AMF component 210, an updatedNR GUTI for the UE 215, and replace a previous NR GUTI with the receivedupdated NR GUTI for the UE 215. RAN component 220 may transmit feedback(e.g., results) of the registration with AMF component 210 to UE 215.For example, the feedback may include the updated NR GUTI and anindication that AMF component 210 is a new serving AMF for UE 215 fornetwork slices associated with the new-allowed NSSAI.

FIG. 3 illustrates an example of a process flow 300 that supportsenabling a network-trigger change of network slices, in accordance withone or more aspects of the present disclosure. In some examples, processflow 300 may implement aspects of wireless communications system 100 and200. UE 305 may be an example of aspects of a respective one of the UEs115 described with reference to FIGS. 1 or 2. AMF component 310, and AMFcomponent 315 may be an example of aspects of a respective one of theAMF components described with reference to FIG. 2.

In the following description of the process flow 300, the operationsbetween UE 305, AMF component 310, or AMF component 315 may betransmitted in a different order than the exemplary order shown, or theoperations performed by UE 305, AMF component 310, or AMF component 315may be performed in different orders or at different times. Certainoperations may also be left out of the process flow 300, or otheroperations may be added to the process flow 300.

At 320, AMF component 310 may identify a request to modifycurrent-allowed network slice supported by UE 305 based on anetwork-trigger. At 325, AMF component 310 may identify new-allowednetwork slices for the UE 305. At 330, AMF component 310 may select atarget AMF. In some examples, AMF component 310 may select the targetAMF based on the new-allowed network slices, where the target AMF isaccessible by the source AMF. In some cases, AMF component 310 maydetermine that UE 305 has an NSI associated with at least one NSSAI of acurrent-allowed S-NSSAI, and identify that an active NSI is supported inthe new-allowed network slices. At 335, AMF component 310 may trigger anAMF relocation. In some examples, AMF component 310 may trigger the AMFrelocation based on selecting the target AMF. AMF component 310 maytransmit AMF relocation request, at 340 to AMF component 315.

At 345, AMF component 315 may allocate a NR GUTI. For example, AMFcomponent 315 may allocate the NR GUTI for the UE 305 based on thetriggered AMF relocation. At 350, AMF component 315 may transmit to UE305 a configuration request message. The configuration request messagemay include the NR GUTI, an updated status of an existing UE PDU session(or multiple existing UE PDU sessions), or the new-allowed networkslices, or a combination thereof. In some cases, the NR GUTI may be amodified version of a previous NR GUTI assigned to UE 305.

At 355, UE 305 may release PDU sessions. In some cases, UE 305 mayreceive, from AMF component 310, the configuration message including theNR GUTI associated with AMF component 315, a status of an existingactive PDU session of the UE 305, or new-allowed network slices, or acombination thereof. UE 305 may store information associated with thenew-allowed network slices and NR GUTI. UE 305 may also identify anactive PDU session based on the status of existing active PDU sessioninformation included in the configuration message, the identified activePDU session may be unsupported by the new-allowed network slices. As aresult, UE 305 may locally release the identified PDU session. In somecases, UE 305 may identify local UE PDU session status for one or moreactive PDU sessions. In addition, UE 305 may receive the updated statusassociated with UE PDU sessions. UE 305 may release the PDU sessionsthat were supported in the local UE PDU session status, but are notsupported in the received updated status. For example, UE 305 maycompare the local UE PDU session status with the received updatedstatus. Based on the comparison UE 305 may identify a change in UE PDUsessions. That is, UE 305 may identify that some or all PDU sessionsassociated with the local UE PDU session status are no longer supportedin the received updated status. In this case, UE 305 may release the PDUsessions that are no longer supported. In addition, the PDU sessionsthat are no longer supported may have already been released by thenetwork.

FIG. 4 illustrates an example of a process flow 400 that supportsenabling a network-trigger change of network slices, in accordance withone or more aspects of the present disclosure. In some examples, processflow 400 may implement aspects of wireless communications system 100 and200. UE 405 may be an example of aspects of a respective one of the UEs115 described with reference to FIGS. 1 through 3. AMF component 410,and RAN component 415 may be an example of aspects of a respective oneof the AMF components and RAN component described with reference to FIG.2.

In the following description of the process flow 400, the operationsbetween UE 405, AMF component 410, or RAN component 415 may betransmitted in a different order than the exemplary order shown, or theoperations performed by UE 405, AMF component 410, or RAN component 415may be performed in different orders or at different times. Certainoperations may also be left out of the process flow 400, or otheroperations may be added to the process flow 400.

At 420, AMF component 410 may identify to modify current-allowed networkslice(s), used by UE 405 based on a network-trigger. At 425, AMFcomponent 410 may identify new-allowed network slice(s), for the UE 405.At 430, AMF component 410 may identify a target AMF based on thenew-allowed network slices. In some cases, AMF component 410 maydetermine that the target AMF associated with the new-allowed networkslices is inaccessible by AMF component 410. Alternatively, AMFcomponent 410 may determine that the target AMF associated with thenew-allowed network slices is accessible by AMF component 410.Additionally, AMF component may determine that no new AMF can beselected. At 435, AMF component 410 may transmit a de-registrationrequest to the UE 405. In some cases, AMF component 410 may transmit thede-registration request to UE 405 based on determining that the targetAMF is inaccessible or that no target AMF can be selected, by the AMFcomponent 410. The de-registration request may include an indication toperform a re-registration procedure, the identified new-allowed networkslices, or a code indicating that the de-registration request is inresponse to a change of supported network slices, or a combinationthereof.

At 440, UE 405 may identify new-allowed network slice(s). In some cases,UE 405 may identify new-allowed network slice(s) based on the receivedde-registration request. At 445, UE 405 may generate a request forregistering the set of network slices. UE 405 may, in some cases,generate the request for registering the set of network slices based onthe code. At 450, UE 405 transmits a registration request. UE 405 maytransmit the registration request to register the new-allowed networkslice(s) to RAN component 415. In some examples, based on the code, UE405 may transmit the request without providing a GUTI to RAN component415. At 455, RAN component 415 may select a target AMF to serve UE 405.In some cases, RAN component 415 may select a target AMF to server UE405 based on the registration request.

FIG. 5 shows a block diagram 500 of a wireless device 505 that supportsenabling a network-trigger change of network slices, in accordance withone or more aspects of the present disclosure. Wireless device 505 maybe an example of aspects of a network entity AMF as described herein.Wireless device 505 may include receiver 510, network entity networkslice manager 515, and transmitter 520. Wireless device 505 may alsoinclude a processor. Each of these components may be in communicationwith one another (e.g., via one or more buses).

Receiver 510 may receive information such as packets, user data, orcontrol information associated with various information channels (e.g.,control channels, data channels, and information related to enable anetwork-trigger change of network slices, etc.). Information may bepassed on to other components of the device. The receiver 510 may be anexample of aspects of the transceiver 835 described with reference toFIG. 8. The receiver 510 may utilize a single antenna or a set ofantennas.

Network entity network slice manager 515 may be an example of aspects ofthe network entity network slice manager 815 described with reference toFIG. 8.

Network entity network slice manager 515 and/or at least some of itsvarious sub-components may be implemented in hardware, software executedby a processor, firmware, or any combination thereof. If implemented insoftware executed by a processor, the functions of the network entitynetwork slice manager 515 and/or at least some of its varioussub-components may be executed by a general-purpose processor, a digitalsignal processor (DSP), an application-specific integrated circuit(ASIC), an field-programmable gate array (FPGA) or other programmablelogic device, discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed in the present disclosure.

The network entity network slice manager 515 and/or at least some of itsvarious sub-components may be physically located at various positions,including being distributed such that portions of functions areimplemented at different physical locations by one or more physicaldevices. In some examples, network entity network slice manager 515and/or at least some of its various sub-components may be a separate anddistinct component in accordance with various aspects of the presentdisclosure. In other examples, network entity network slice manager 515and/or at least some of its various sub-components may be combined withone or more other hardware components, including but not limited to anI/O component, a transceiver, a network server, another computingdevice, one or more other components described in the presentdisclosure, or a combination thereof in accordance with various aspectsof the present disclosure.

Network entity network slice manager 515 may determine to modifycurrent-allowed network slices used by a UE based on a network-trigger,identify new-allowed network slices for the UE based on the determining,select a target AMF based on the new-allowed network slices, where thetarget AMF is accessible by the source AMF, and trigger an AMFrelocation based on the selecting. The network entity network slicemanager 515 may also receive, from a source AMF, an AMF relocationrequest for a UE currently served by the source AMF. The AMF relocationrequest may include new-allowed network slices and UE contextinformation. The network entity network slice manager 515 may allocatean updated GUTI for the UE based on the AMF relocation request, andtransmit to the UE a configuration request message including the updatedNR GUTI, an updated status of an existing PDU session, or thenew-allowed NSSAI, or a combination thereof.

The network entity network slice manager 515 may also determine tomodify current-allowed network slice used by a UE based on a receivednetwork-trigger, identify new-allowed network slices for the UE based onthe determining, and determine that a target AMF associated with thenew-allowed network slices is inaccessible by the source AMF. Thenetwork entity network slice manager 515 may also receive, from a UE aRRC connection request including NSSAI, select a target AMF to serve theUE based on the NSSAI received in the RRC connection request, establishan N2 signaling connection with the selected AMF, and transmit a NASmessage received from the UE to the selected AMF using the N2 signalingconnection.

Transmitter 520 may transmit signals generated by other components ofthe device. In some examples, the transmitter 520 may be collocated witha receiver 510 in a transceiver module. For example, the transmitter 520may be an example of aspects of the transceiver 835 described withreference to FIG. 8. The transmitter 520 may utilize a single antenna ora set of antennas.

It should be noted that the methods described above describe possibleimplementations, and that the operations and the blocks may berearranged or otherwise modified and that other implementations arepossible. Furthermore, aspects from two or more of the methods may becombined.

FIG. 6 shows a block diagram 600 of a wireless device 605 that supportsenabling a network-trigger change of network slices, in accordance withone or more aspects of the present disclosure. Wireless device 605 maybe an example of aspects of a wireless device 505 or an AMF as describedwith reference to FIG. 5. Wireless device 605 may include receiver 610,network entity network slice manager 615, and transmitter 620. Wirelessdevice 605 may also include a processor. Each of these components may bein communication with one another (e.g., via one or more buses).

Receiver 610 may receive information such as packets, user data, orcontrol information associated with various information channels (e.g.,control channels, data channels, and information related to enabling anetwork-trigger change of network slices, etc.). Information may bepassed on to other components of the device. The receiver 610 may be anexample of aspects of the transceiver 835 described with reference toFIG. 8. The receiver 610 may utilize a single antenna or a set ofantennas.

Network entity network slice manager 615 may be an example of aspects ofthe network entity network slice manager 815 described with reference toFIG. 8. Network entity network slice manager 615 may also includenetwork slice modification component 625, network slice identificationcomponent 630, AMF determination component 635, AMF relocation triggercomponent 640, request component 645, allocation component 650, andconnection component 655.

Network slice modification component 625 may determine to modifycurrent-allowed network slices used by a UE based on a network-triggerand determine to modify current-allowed network slice used by a UE basedon a received network-trigger. Network slice identification component630 may identify new-allowed network slices for the UE based on thedetermining, determine that the UE has an active network slice instance(NSI) associated with at least one network selection assistanceinformation (NSSAI), and identify that an active NSI is supported by thenew-allowed network slices.

AMF determination component 635 may select a target AMF based on thenew-allowed network slices, where the target AMF is accessible by thesource AMF. The AMF determination component 635 may determine that atarget AMF associated with the new-allowed network slices isinaccessible by the source AMF, and transmit a de-registration requestto the UE based on determining that the target AMF is inaccessible bythe source AMF. The AMF determination component 635 may select a targetAMF to serve the UE based on the NSSAI received in the RRC connectionrequest. The AMF determination component 635 may receive, from theselected AMF, an updated NR GUTI for the UE, and replace a previous NRGUTI with the received updated NR GUTI for the UE. In some cases, thede-registration request includes an indication to perform are-registration procedure, the identified new-allowed network slices, ora code indicating that the de-registration request is in response to achange of supported network slices, or a combination thereof.

AMF relocation trigger component 640 may trigger an AMF relocation basedon the selecting and transmit an AMF relocation request to the targetAMF based on the new-allowed NSSAI, where the AMF relocation requestincludes a status of all existing PDU session associated with the activeNSI that are supported and active, or a NR globally unique temporaryidentifier (GUTI), or both.

Request component 645 may receive, from a source AMF, an AMF relocationrequest for a UE currently served by the source AMF, the AMF relocationrequest including new-allowed network slices and UE context information.Request component 645 may transmit to the UE a configuration requestmessage including the updated NR GUTI, an updated status of an existingPDU session, or the new-allowed NSSAI, or a combination thereof, andreceive, from a UE a RRC connection request including NSSAI. In somecases, the UE context information includes a status of an existing PDUsession associated with an active NSI or a current NR GUTI, or acombination thereof. Allocation component 650 may allocate an updated NRGUTI for the UE based on the AMF relocation request.

Connection component 655 may establish an N2 signaling connection withthe selected AMF, transmit a NAS message received from the UE to theselected AMF using the N2 signaling connection, and transmit, to aprevious serving AMF of the UE, a request to release an N2 signalingconnection.

Transmitter 620 may transmit signals generated by other components ofthe device. In some examples, the transmitter 620 may be collocated witha receiver 610 in a transceiver module. For example, the transmitter 620may be an example of aspects of the transceiver 835 described withreference to FIG. 8. The transmitter 620 may utilize a single antenna ora set of antennas.

FIG. 7 shows a block diagram 700 of a network entity network slicemanager 715 that supports enabling a network-trigger change of networkslices in accordance with one or more aspects of the present disclosure.The network entity network slice manager 715 may be an example ofaspects of a network entity network slice manager 515, a network entitynetwork slice manager 615, or a network entity network slice manager 815described with reference to FIGS. 5, 6, and 8. The network entitynetwork slice manager 715 may include network slice modificationcomponent 720, network slice identification component 725, AMFdetermination component 730, AMF relocation trigger component 735,request component 740, allocation component 745, connection component750, reporting component 755, and release component 760. Each of thesemodules may communicate, directly or indirectly, with one another (e.g.,via one or more buses).

Network slice modification component 720 may determine to modifycurrent-allowed network slices used by a UE based on a network-triggerand determine to modify current-allowed network slice used by a UE basedon a received network-trigger.

Network slice identification component 725 may identify new-allowednetwork slices for the UE based on the determining, determine that theUE has an active network slice instance (NSI) associated with at leastone network selection assistance information (NSSAI), and identify thatan active NSI is supported by the new-allowed network slices.

AMF determination component 730 may select a target AMF based on thenew-allowed network slices, where the target AMF is accessible by thesource AMF, determine that a target AMF associated with the new-allowednetwork slices is inaccessible by the source AMF, and transmit ade-registration request to the UE based on determining that the targetAMF is inaccessible by the source AMF. AMF determination component 730may select a target AMF to serve the UE based on the NSSAI received inthe RRC connection request. AMF determination component 730 may receive,from the selected AMF, an updated NR GUTI for the UE, and replace aprevious NR GUTI with the received updated NR GUTI for the UE. In somecases, the de-registration request includes an indication to perform are-registration procedure, the identified new-allowed network slices, ora code indicating that the de-registration request is in response to achange of supported network slices, or a combination thereof.

AMF relocation trigger component 735 may trigger an AMF relocation basedon the selecting and transmit an AMF relocation request to the targetAMF based on the new-allowed NSSAI, where the AMF relocation requestincludes a status of all existing PDU session associated with the activeNSI that are supported and active, or a NR GUTI, or both.

Request component 740 may receive, from a source AMF, an AMF relocationrequest for a UE currently served by the source AMF, the AMF relocationrequest including new-allowed network slices and UE context information,and transmit to the UE a configuration request message including theupdated NR GUTI, an updated status of an existing PDU session, or thenew-allowed NSSAI, or a combination thereof. Request component 740 mayreceive, from a UE, a RRC connection request including NSSAI. In somecases, the UE context information includes a status of an existing PDUsession associated with an active NSI or a current NR GUTI, or acombination thereof.

Allocation component 745 may allocate an updated NR GUTI for the UEbased on the AMF relocation request. Connection component 750 mayestablish an N2 signaling connection with the selected AMF, transmit aNAS message received from the UE to the selected AMF using the N2signaling connection, and transmit, to a previous serving AMF of the UE,a request to release an N2 signaling connection. Reporting component 755may generate a status report indicating a status of all existing PDUsessions associated with the active NSI.

Release component 760 may trigger a release procedure of an active PDUsession associated with the current-allowed network slices based onidentifying that the active PDU session is not supported by thenew-allowed network slices, trigger a release procedure of an active PDUsession associated with current-allowed network slices that areunsupported by the new-allowed network slices, and release UE contextincluding a status report of active PDU session or a NR GUTI, or bothbased on the triggering. In some cases, the triggering the releaseprocedure based on direct signaling to the UE.

FIG. 8 shows a diagram of a system 800 including a device 805 thatsupports enabling a network-trigger change of network slices, inaccordance with one or more aspects of the present disclosure. Device805 may be an example of or include the components of wireless device505, wireless device 605, or an AMF as described above, e.g., withreference to FIGS. 5 and 6. Device 805 may include components forbi-directional voice and data communications including components fortransmitting and receiving communications, including network entitynetwork slice manager 815, processor 820, memory 825, software 830,transceiver 835, and I/O controller 840. These components may be inelectronic communication via one or more buses (e.g., bus 810).

Processor 820 may include an intelligent hardware device, (e.g., ageneral-purpose processor, a DSP, a central processing unit (CPU), amicrocontroller, an ASIC, an FPGA, a programmable logic device, adiscrete gate or transistor logic component, a discrete hardwarecomponent, or any combination thereof). In some cases, processor 820 maybe configured to operate a memory array using a memory controller. Inother cases, a memory controller may be integrated into processor 820.Processor 820 may be configured to execute computer-readableinstructions stored in a memory to perform various functions (e.g.,functions or tasks supporting enabling a network-trigger change ofnetwork slices).

Memory 825 may include random access memory (RAM) and read only memory(ROM). The memory 825 may store computer-readable, computer-executablesoftware 830 including instructions that, when executed, cause theprocessor to perform various functions described herein. In some cases,the memory 825 may contain, among other things, a basic input/outputsystem (BIOS) which may control basic hardware or software operationsuch as the interaction with peripheral components or devices. Software830 may include code to implement aspects of the present disclosure,including code to support enabling a network-trigger change of networkslices. Software 830 may be stored in a non-transitory computer-readablemedium such as system memory or other memory. In some cases, thesoftware 830 may not be directly executable by the processor but maycause a computer (e.g., when compiled and executed) to perform functionsdescribed herein.

Transceiver 835 may communicate bi-directionally, via one or moreantennas, wired, or wireless links as described above. For example, thetransceiver 835 may represent a wireless transceiver and may communicatebi-directionally with another wireless transceiver. The transceiver 835may also include a modem to modulate the packets and provide themodulated packets to the antennas for transmission, and to demodulatepackets received from the antennas.

I/O controller 840 may manage input and output signals for device 805.I/O controller 840 may also manage peripherals not integrated intodevice 805. In some cases, I/O controller 840 may represent a physicalconnection or port to an external peripheral. In some cases, I/Ocontroller 840 may utilize an operating system such as iOS®, ANDROID®,MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operatingsystem. In other cases, I/O controller 840 may represent or interactwith a modem, a keyboard, a mouse, a touchscreen, or a similar device.In some cases, I/O controller 840 may be implemented as part of aprocessor. In some cases, a user may interact with device 805 via I/Ocontroller 840 or via hardware components controlled by I/O controller840.

FIG. 9 shows a block diagram 900 of a wireless device 905 that supportsenabling a network-trigger change of network slices, in accordance withone or more aspects of the present disclosure. Wireless device 905 maybe an example of aspects of a UE 115 as described herein. Wirelessdevice 905 may include receiver 910, UE network slice manager 915, andtransmitter 920. Wireless device 905 may also include a processor. Eachof these components may be in communication with one another (e.g., viaone or more buses).

Receiver 910 may receive information such as packets, user data, orcontrol information associated with various information channels (e.g.,control channels, data channels, and information related to enabling anetwork-trigger change of network slices, etc.). Information may bepassed on to other components of the device. The receiver 910 may be anexample of aspects of the transceiver 1235 described with reference toFIG. 12. The receiver 910 may utilize a single antenna or a set ofantennas. UE network slice manager 915 may be an example of aspects ofthe UE network slice manager 1215 described with reference to FIG. 12.

UE network slice manager 915 and/or at least some of its varioussub-components may be implemented in hardware, software executed by aprocessor, firmware, or any combination thereof. If implemented insoftware executed by a processor, the functions of the UE network slicemanager 915 and/or at least some of its various sub-components may beexecuted by a general-purpose processor, a DSP, an ASIC, an FPGA orother programmable logic device, discrete gate or transistor logic,discrete hardware components, or any combination thereof designed toperform the functions described in the present disclosure.

The UE network slice manager 915 and/or at least some of its varioussub-components may be physically located at various positions, includingbeing distributed such that portions of functions are implemented atdifferent physical locations by one or more physical devices. In someexamples, UE network slice manager 915 and/or at least some of itsvarious sub-components may be a separate and distinct component inaccordance with various aspects of the present disclosure. In otherexamples, UE network slice manager 915 and/or at least some of itsvarious sub-components may be combined with one or more other hardwarecomponents, including but not limited to an I/O component, atransceiver, a network server, another computing device, one or moreother components described in the present disclosure, or a combinationthereof in accordance with various aspects of the present disclosure.

UE network slice manager 915 may receive, from a source AMF, aconfiguration message including a NR GUTI associated with a target AMF,a status of an existing active PDU session of the UE, or new-allowednetwork slices, or a combination thereof, store information associatedwith the new-allowed network slices and NR GUTI, identify an active PDUsession based on the status of existing active PDU session informationincluded in the configuration message, the identified active PDU sessionis unsupported by the new-allowed network slices, and locally releasethe identified active PDU session. The UE network slice manager 915 mayalso identify a re-registration request and a code indicating a requestto register a set of network slices associated with a new-allowednetwork slice based on a received de-registration request from a sourceAMF that is serving the UE, identify the new-allowed network slicesbased on the received de-registration request, and generate a requestfor registering the set of network slices based on the code.

Transmitter 920 may transmit signals generated by other components ofthe device. In some examples, the transmitter 920 may be collocated witha receiver 910 in a transceiver module. For example, the transmitter 920may be an example of aspects of the transceiver 1235 described withreference to FIG. 12. The transmitter 920 may utilize a single antennaor a set of antennas.

FIG. 10 shows a block diagram 1000 of a wireless device 1005 thatsupports enabling a network-trigger change of network slices, inaccordance with one or more aspects of the present disclosure. Wirelessdevice 1005 may be an example of aspects of a wireless device 905 or aUE 115 as described with reference to FIG. 9. Wireless device 1005 mayinclude receiver 1010, UE network slice manager 1015, and transmitter1020. Wireless device 1005 may also include a processor. Each of thesecomponents may be in communication with one another (e.g., via one ormore buses).

Receiver 1010 may receive information such as packets, user data, orcontrol information associated with various information channels (e.g.,control channels, data channels, and information related to enabling anetwork-trigger change of network slices, etc.). Information may bepassed on to other components of the device. The receiver 1010 may be anexample of aspects of the transceiver 1235 described with reference toFIG. 12. The receiver 1010 may utilize a single antenna or a set ofantennas.

UE network slice manager 1015 may be an example of aspects of the UEnetwork slice manager 1215 described with reference to FIG. 12. UEnetwork slice manager 1015 may also include configuration component1025, session component 1030, release component 1035, request component1040, and network slice identification component 1045.

Configuration component 1025 may receive, from a source AMF, aconfiguration message including a NR GUTI associated with a target AMF,a status of an existing active PDU session of the UE, or new-allowednetwork slices, or a combination thereof and store informationassociated with the new-allowed network slices and NR GUTI. Sessioncomponent 1030 may identify an active PDU session based on the status ofexisting active PDU session information included in the configurationmessage, the identified active PDU session is unsupported by thenew-allowed network slices.

Release component 1035 may locally release the identified active PDUsession. Request component 1040 may identify a re-registration requestand a code indicating a request to register a set of network slicesassociated with a new-allowed network slice based on a receivedde-registration request from a source AMF that is serving the UE andgenerate a request for registering the set of network slices based onthe code.

Network slice identification component 1045 may identify the new-allowednetwork slices based on the received de-registration request, storeinformation associated with the new-allowed network slices, where theinformation includes NSSAI, and remove a current NR GUTI based on thecode.

Transmitter 1020 may transmit signals generated by other components ofthe device. In some examples, the transmitter 1020 may be collocatedwith a receiver 1010 in a transceiver module. For example, thetransmitter 1020 may be an example of aspects of the transceiver 1235described with reference to FIG. 12. The transmitter 1020 may utilize asingle antenna or a set of antennas.

FIG. 11 shows a block diagram 1100 of a UE network slice manager 1115that supports enabling a network-trigger change of network slices, inaccordance with one or more aspects of the present disclosure. The UEnetwork slice manager 1115 may be an example of aspects of a UE networkslice manager 1215 described with reference to FIGS. 9, 10, and 12. TheUE network slice manager 1115 may include configuration component 1120,session component 1125, release component 1130, request component 1135,network slice identification component 1140, and connection component1145. Each of these modules may communicate, directly or indirectly,with one another (e.g., via one or more buses).

Configuration component 1120 may receive, from a source AMF, aconfiguration message including a NR GUTI associated with a target AMF,a status of an existing active PDU session of the UE, or new-allowednetwork slices, or a combination thereof and store informationassociated with the new-allowed network slices and NR GUTI. Sessioncomponent 1125 may identify an active PDU session based on the status ofexisting active PDU session information included in the configurationmessage, the identified active PDU session is unsupported by thenew-allowed network slices. Release component 1130 may locally releasethe identified active PDU session.

Request component 1135 may identify a re-registration request and a codeindicating a request to register a set of network slices associated witha new-allowed network slice based on a received de-registration requestfrom a source access and management function (AMF) that is serving theUE and generate a request for registering the set of network slicesbased on the code. Network slice identification component 1140 mayidentify the new-allowed network slices based on the receivedde-registration request, store information associated with thenew-allowed network slices, where the information includes NSSAI, andremove a current NR GUTI based on the code.

Connection component 1145 may transmit a request to re-establish theconnection based on the indication to re-establish the connection, wherethe request includes the NSSAI request, and transmit a new RRCreconfiguration request message including a the NSSAI request, or a codeindicating signaling path configuration, or a current NR GUTI, or acombination thereof. Connection component 1145 may transmit a Nwumessage including the NSSAI request, or a code indicating signaling pathconfiguration, or a current NR GUTI, or a combination thereof. In somecases, an upper layer of the UE transmits to a lower layer of the UE: anindication to release a connection with a RAN and to re-establish theconnection, or the NSSAI request, or an indication to refrain fromproviding a NR GUTI, or a combination thereof. In some cases, the upperlayer includes a NAS layer and the lower layer includes an AS layer. Insome cases, the connection includes a RRC connection. In some cases, theUE performs a RRC connection release procedure or an RRC connectionestablishment procedure, or both based on the indication to release aconnection with a RAN and to re-establish the connection. In some cases,the connection includes an (IPsec) tunnel connection. In some cases, theUE performs an IPsec tunnel release procedure or an IPsec tunnelestablishment procedure, or both based on the indication to release aconnection with a RAN and to re-establish the connection. In some cases,the Nwu message includes an IKEv2 INFORMATIONAL message, or areconfigure signaling connection message, or both.

FIG. 12 shows a diagram of a system 1200 including a device 1205 thatsupports enabling a network-trigger change of network slices, inaccordance with one or more aspects of the present disclosure. Device1205 may be an example of or include the components of UE 115 asdescribed above, e.g., with reference to FIG. 1. Device 1205 may includecomponents for bi-directional voice and data communications includingcomponents for transmitting and receiving communications, including UEnetwork slice manager 1215, processor 1220, memory 1225, software 1230,transceiver 1235, antenna 1240, and I/O controller 1245. Thesecomponents may be in electronic communication via one or more buses(e.g., bus 1210). Device 1205 may communicate wirelessly with one ormore base stations 105.

Processor 1220 may include an intelligent hardware device, (e.g., ageneral-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, anFPGA, a programmable logic device, a discrete gate or transistor logiccomponent, a discrete hardware component, or any combination thereof).In some cases, processor 1220 may be configured to operate a memoryarray using a memory controller. In other cases, a memory controller maybe integrated into processor 1220. Processor 1220 may be configured toexecute computer-readable instructions stored in a memory to performvarious functions (e.g., functions or tasks supporting enabling anetwork-trigger change of network slices).

Memory 1225 may include RAM and ROM. The memory 1225 may storecomputer-readable, computer-executable software 1230 includinginstructions that, when executed, cause the processor to perform variousfunctions described herein. In some cases, the memory 1225 may contain,among other things, a BIOS which may control basic hardware or softwareoperation such as the interaction with peripheral components or devices.

Software 1230 may include code to implement aspects of the presentdisclosure, including code to support enabling a network-trigger changeof network slices. Software 1230 may be stored in a non-transitorycomputer-readable medium such as system memory or other memory. In somecases, the software 1230 may not be directly executable by the processorbut may cause a computer (e.g., when compiled and executed) to performfunctions described herein.

Transceiver 1235 may communicate bi-directionally, via one or moreantennas, wired, or wireless links as described above. For example, thetransceiver 1235 may represent a wireless transceiver and maycommunicate bi-directionally with another wireless transceiver. Thetransceiver 1235 may also include a modem to modulate the packets andprovide the modulated packets to the antennas for transmission, and todemodulate packets received from the antennas. In some cases, thewireless device may include a single antenna 1240. However, in somecases the device may have more than one antenna 1240, which may becapable of concurrently transmitting or receiving multiple wirelesstransmissions.

I/O controller 1245 may manage input and output signals for device 1205.I/O controller 1245 may also manage peripherals not integrated intodevice 1205. In some cases, I/O controller 1245 may represent a physicalconnection or port to an external peripheral. In some cases, I/Ocontroller 1245 may utilize an operating system such as iOS®, ANDROID®,MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operatingsystem. In other cases, I/O controller 1245 may represent or interactwith a modem, a keyboard, a mouse, a touchscreen, or a similar device.In some cases, I/O controller 1245 may be implemented as part of aprocessor. In some cases, a user may interact with device 1205 via I/Ocontroller 1245 or via hardware components controlled by I/O controller1245.

FIG. 13 shows a flowchart illustrating a method 1300 for enabling anetwork-trigger change of network slices, in accordance with one or moreaspects of the present disclosure. The operations of method 1300 may beimplemented by a AMF or its components as described herein. For example,the operations of method 1300 may be performed by a network entitynetwork slice manager as described with reference to FIGS. 5 through 8.In some examples, a network entity may execute a set of codes to controlthe functional elements of the device to perform the functions describedbelow. Additionally or alternatively, the network entity may performaspects of the functions described below using special-purpose hardware.

At 1305 the network entity may determine to modify current-allowednetwork slices used by a UE based on a network-trigger. The operationsof 1305 may be performed according to the methods described herein. Incertain examples, aspects of the operations of 1305 may be performed bya network slice modification component as described with reference toFIGS. 5 through 8.

At 1310 the network entity may identify new-allowed network slices forthe UE based on the determining. The operations of 1310 may be performedaccording to the methods described herein. In certain examples, aspectsof the operations of 1310 may be performed by a network sliceidentification component as described with reference to FIGS. 5 through8.

At 1315 the network entity may select a target AMF based on thenew-allowed network slices, the target AMF is accessible by the sourceAMF. The operations of 1315 may be performed according to the methodsdescribed herein. In certain examples, aspects of the operations of 1315may be performed by a AMF determination component as described withreference to FIGS. 5 through 8.

At 1320 the network entity may trigger an AMF relocation based on theselecting. The operations of 1320 may be performed according to themethods described herein. In certain examples, aspects of the operationsof 1320 may be performed by a AMF relocation trigger component asdescribed with reference to FIGS. 5 through 8.

FIG. 14 shows a flowchart illustrating a method 1400 for enabling anetwork-trigger change of network slices, in accordance with one or moreaspects of the present disclosure. The operations of method 1400 may beimplemented by a network entity e.g., AMF or its components as describedherein. For example, the operations of method 1400 may be performed by anetwork entity network slice manager as described with reference toFIGS. 5 through 8. In some examples, a network entity may execute a setof codes to control the functional elements of the device to perform thefunctions described below. Additionally or alternatively, the networkentity may perform aspects of the functions described below usingspecial-purpose hardware.

At 1405 the network entity may receive, from a source AMF, an AMFrelocation request for a UE currently served by the source AMF, the AMFrelocation request including new-allowed network slices and UE contextinformation. The operations of 1405 may be performed according to themethods described herein. In certain examples, aspects of the operationsof 1405 may be performed by a request component as described withreference to FIGS. 5 through 8.

At 1410 the network entity may allocate an updated NR GUTI for the UEbased on the AMF relocation request. The operations of 1410 may beperformed according to the methods described herein. In certainexamples, aspects of the operations of 1410 may be performed by anallocation component as described with reference to FIGS. 5 through 8.

At 1415 the network entity may transmit to the UE a configurationrequest message including the updated NR GUTI, an updated status of anexisting PDU session, or the new-allowed NSSAI, or a combinationthereof. The operations of 1415 may be performed according to themethods described herein. In certain examples, aspects of the operationsof 1415 may be performed by a request component as described withreference to FIGS. 5 through 8.

FIG. 15 shows a flowchart illustrating a method 1500 for enabling anetwork-trigger change of network slices, in accordance with one or moreaspects of the present disclosure. The operations of method 1500 may beimplemented by a UE 115 or its components as described herein. Forexample, the operations of method 1500 may be performed by a UE networkslice manager as described with reference to FIGS. 9 through 12. In someexamples, a UE 115 may execute a set of codes to control the functionalelements of the device to perform the functions described below.Additionally or alternatively, the UE 115 may perform aspects of thefunctions described below using special-purpose hardware.

At 1505 the UE 115 may receive, from a source AMF, a configurationmessage including a NR GUTI associated with a target AMF, a status of anexisting active PDU session of the UE 115, or new-allowed networkslices, or a combination thereof. The operations of 1505 may beperformed according to the methods described herein. In certainexamples, aspects of the operations of 1505 may be performed by aconfiguration component as described with reference to FIGS. 9 through12.

At 1510 the UE 115 may store information associated with the new-allowednetwork slices and NR GUTI. The operations of 1510 may be performedaccording to the methods described herein. In certain examples, aspectsof the operations of 1510 may be performed by a configuration componentas described with reference to FIGS. 9 through 12.

At 1515 the UE 115 may identify an active PDU session based on thestatus of existing active PDU session information included in theconfiguration message, the identified active PDU session is unsupportedby the new-allowed network slices. The operations of 1515 may beperformed according to the methods described herein. In certainexamples, aspects of the operations of 1515 may be performed by asession component as described with reference to FIGS. 9 through 12.

At 1520 the UE 115 may locally release the identified active PDUsession. The operations of 1520 may be performed according to themethods described herein. In certain examples, aspects of the operationsof 1520 may be performed by a release component as described withreference to FIGS. 9 through 12.

FIG. 16 shows a flowchart illustrating a method 1600 for enabling anetwork-trigger change of network slices, in accordance with one or moreaspects of the present disclosure. The operations of method 1600 may beimplemented by a network entity e.g., AMF or its components as describedherein. For example, the operations of method 1600 may be performed by anetwork entity network slice manager as described with reference toFIGS. 5 through 8. In some examples, a network entity may execute a setof codes to control the functional elements of the device to perform thefunctions described below. Additionally or alternatively, the networkentity may perform aspects of the functions described below usingspecial-purpose hardware.

At 1605 the network entity may determine to modify current-allowednetwork slice used by a UE based on a received network-trigger. Theoperations of 1605 may be performed according to the methods describedherein. In certain examples, aspects of the operations of 1605 may beperformed by a network slice modification component as described withreference to FIGS. 5 through 8.

At 1610 the network entity may identify new-allowed network slices forthe UE based on the determining. The operations of 1610 may be performedaccording to the methods described herein. In certain examples, aspectsof the operations of 1610 may be performed by a network sliceidentification component as described with reference to FIGS. 5 through8.

At 1615 the network entity may determine that a target AMF associatedwith the new-allowed network slices is inaccessible by the source AMF.The operations of 1615 may be performed according to the methodsdescribed herein. In certain examples, aspects of the operations of 1615may be performed by a AMF determination component as described withreference to FIGS. 5 through 8.

At 1620 the network entity may identify a re-registration request and acode indicating a request to register a set of network slices associatedwith a new-allowed network slice based on a received de-registrationrequest from a source AMF that is serving the UE. The operations of 1620may be performed according to the methods described herein. In certainexamples, aspects of the operations of 1620 may be performed by arequest component as described with reference to FIGS. 5 through 8.

At 1625 the network entity may identify the new-allowed network slicesbased on the received de-registration request. The operations of 1625may be performed according to the methods described herein. In certainexamples, aspects of the operations of 1625 may be performed by anetwork slice identification component as described with reference toFIGS. 5 through 8.

At 1630 the network entity may generate a request for registering theset of network slices based on the code. The operations of 1630 may beperformed according to the methods described herein. In certainexamples, aspects of the operations of 1630 may be performed by arequest component as described with reference to FIGS. 5 through 8.

FIG. 17 shows a flowchart illustrating a method 1700 for enabling anetwork-trigger change of network slices, in accordance with one or moreaspects of the present disclosure. The operations of method 1700 may beimplemented by a UE 115 or its components as described herein. Forexample, the operations of method 1700 may be performed by a UE networkslice manager as described with reference to FIGS. 9 through 12. In someexamples, a UE 115 may execute a set of codes to control the functionalelements of the device to perform the functions described below.Additionally or alternatively, the UE 115 may perform aspects of thefunctions described below using special-purpose hardware.

At 1705 the UE 115 may receive a de-registration request from a sourceAMF. In some cases, UE 115 may identify a re-registration request and acode indicating a request to register one or more new network slicesassociated with a new-allowed network slice based on the receivedde-registration request from the source AMF serving the UE 115. Theoperations of 1705 may be performed according to the methods describedherein. In certain examples, aspects of the operations of 1705 may beperformed by a request component as described with reference to FIGS. 9through 12.

At 1710 the UE 115 may generate a request for registering one or morenetwork slices based on a code (e.g., indicating a request to registerone or more new network slices associated with a new-allowed networkslice), where an upper layer of the UE transmits to a lower layer of theUE: an indication to release a connection with a RAN and to re-establishthe connection, or a NSSAI request, or an indication to refrain fromproviding a NR GUTI, or a combination thereof. Additionally, in someexamples, upon UE 115 receiving the de-registration request including anindication to re-register or the cause code, or both; the upper layer(s)of the UE 115 may indicate to the lower layer(s) of UE 115 to delete anexisting GUTI. In addition the upper layer(s) may indicate to the lowerlayer(s) to transmit a registration request with the one or more newnetwork slices. In some cases, the upper layer is NAS layer and thelower layer is an AS layer. The operations of 1710 may be performedaccording to the methods described herein. In certain examples, aspectsof the operations of 1710 may be performed by a connection component asdescribed with reference to FIGS. 9 through 12.

At 1715 the UE 115 may transmit a request to re-establish the connectionbased on the indication to re-establish the connection. In some cases,the request may include an NSSAI request. In some cases, the connectionmay also be a RRC connection. In this case, UE 115 may perform a RRCconnection release procedure or an RRC connection establishmentprocedure, or both based on the indication to release a connection witha RAN and to re-establish the connection. Alternatively, the connectionmay be a IPsec tunnel connection. In this case, UE 115 may perform anIPsec tunnel release procedure or an IPsec tunnel establishmentprocedure, or both based on the indication to release a connection witha RAN and to re-establish the connection. The operations of 1715 may beperformed according to the methods described herein. In certainexamples, aspects of the operations of 1715 may be performed by aconnection component as described with reference to FIGS. 9 through 12.

FIG. 18 shows a flowchart illustrating a method 1800 for enabling anetwork-trigger change of network slices, in accordance with one or moreaspects of the present disclosure. The operations of method 1800 may beimplemented by a network entity e.g., RAN or its components as describedherein. For example, the operations of method 1800 may be performed by anetwork entity network slice manager as described with reference toFIGS. 5 through 8. In some examples, a network entity may execute a setof codes to control the functional elements of the device to perform thefunctions described below. Additionally or alternatively, the networkentity may perform aspects of the functions described below usingspecial-purpose hardware.

At 1805 the network entity may receive, from a UE a RRC connectionrequest indicating a request to register one or more new network slicesassociated with a new-allowed network slice NSSAI. The operations of1805 may be performed according to the methods described herein. Incertain examples, aspects of the operations of 1805 may be performed bya request component as described with reference to FIGS. 5 through 8.

At 1810 the network entity may select a target AMF to serve the UE basedon the NSSAI received in the RRC connection request. The operations of1810 may be performed according to the methods described herein. Incertain examples, aspects of the operations of 1810 may be performed bya AMF determination component as described with reference to FIGS. 5through 8.

At 1815 the network entity may establish an N2 signaling connection withthe selected AMF. The operations of 1815 may be performed according tothe methods described herein. In certain examples, aspects of theoperations of 1815 may be performed by a connection component asdescribed with reference to FIGS. 5 through 8.

At 1820 the network entity may transmit a NAS message received from theUE to the selected AMF using the N2 signaling connection. The operationsof 1820 may be performed according to the methods described herein. Incertain examples, aspects of the operations of 1820 may be performed bya connection component as described with reference to FIGS. 5 through 8.

FIG. 19 shows a flowchart illustrating a method 1900 for enabling anetwork-trigger change of network slices, in accordance with one or moreaspects of the present disclosure. The operations of method 1900 may beimplemented by a network entity e.g., RAN or its components as describedherein. In some examples, a network entity may execute a set of codes tocontrol the functional elements of the device to perform the functionsdescribed below. Additionally or alternatively, the network entity mayperform aspects of the functions described below using special-purposehardware.

At 1905 the network entity may receive, from a UE, a RRC connectionrequest including NSSAI. The operations of 1905 may be performedaccording to the methods described herein. In certain examples, thenetwork entity may perform aspects of the functions described belowusing special-purpose hardware.

At 1910 the network entity may identify a source AMF associatedcurrent-allowed network slices of the UE based on the NSSAI. Theoperations of 1910 may be performed according to the methods describedherein. In certain examples, the network entity may perform aspects ofthe functions described below using special-purpose hardware.

At 1915 the network entity may determine to modify the NSSAI based on atrigger indication. The operations of 1915 may be performed according tothe methods described herein. In certain examples, the network entitymay perform aspects of the functions described below usingspecial-purpose hardware.

At 1920 the network entity may identify new-allowed network slicessupported for the UE based on the determining. The operations of 1920may be performed according to the methods described herein. In certainexamples, the network entity may perform aspects of the functionsdescribed below using special-purpose hardware.

At 1925 the network entity may select a target AMF to serve the UE basedon the new-allowed network slices. The operations of 1925 may beperformed according to the methods described herein. In certainexamples, the network entity may perform aspects of the functionsdescribed below using special-purpose hardware.

At 1930 the network entity may trigger an AMF relocation based on theselecting, the AMF relocation includes signaling the source AMF toredirect the RRC connection request to the target AMF. The operations of1925 may be performed according to the methods described herein. Incertain examples, the network entity may perform aspects of thefunctions described below using special-purpose hardware.

FIG. 20 shows a flowchart illustrating a method 2000 for enabling anetwork-trigger change of network slices, in accordance with one or moreaspects of the present disclosure. The operations of method 2000 may beimplemented by a network entity e.g., RAN or its components as describedherein. In some examples, a network entity may execute a set of codes tocontrol the functional elements of the device to perform the functionsdescribed below. Additionally or alternatively, the network entity mayperform aspects of the functions described below using special-purposehardware.

At 2005 the network entity may receive, from a UE, a request forrelocation from a source AMF associated with current-allowed networkslices of the UE based on NSSAI. The operations of 2005 may be performedaccording to the methods described herein. In certain examples, thenetwork entity may perform aspects of the functions described belowusing special-purpose hardware.

At 2010 the network entity may determine to modify the NSSAI based on atrigger indication. The operations of 2010 may be performed according tothe methods described herein. In certain examples, the network entitymay perform aspects of the functions described below usingspecial-purpose hardware.

At 2015 the network entity may identify new-allowed network slicessupported for the UE based on the determining. The operations of 2015may be performed according to the methods described herein. In certainexamples, the network entity may perform aspects of the functionsdescribed below using special-purpose hardware.

At 2020 the network entity may select a target AMF to serve the UE basedon the new-allowed network slices. The operations of 2020 may beperformed according to the methods described herein. In certainexamples, the network entity may perform aspects of the functionsdescribed below using special-purpose hardware.

At 2025 the network entity may trigger an AMF relocation based on theselecting, the AMF relocation includes initiating a redirection of theUE from the source AMF to the target AMF. The operations of 2025 may beperformed according to the methods described herein. In certainexamples, the network entity may perform aspects of the functionsdescribed below using special-purpose hardware.

Techniques described herein may be used for various wirelesscommunications systems such as code division multiple access (CDMA),time division multiple access (TDMA), frequency division multiple access(FDMA), orthogonal frequency division multiple access (OFDMA), singlecarrier frequency division multiple access (SC-FDMA), and other systems.The terms “system” and “network” are often used interchangeably. A codedivision multiple access (CDMA) system may implement a radio technologysuch as CDMA2000, Universal Terrestrial Radio Access (UTRA), etc.CDMA2000 covers IS-2000, IS-95, and IS-856 standards. IS-2000 Releasesmay be commonly referred to as CDMA2000 IX, IX, etc. IS-856 (TIA-856) iscommonly referred to as CDMA2000 1×EV-DO, High Rate Packet Data (HRPD),etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. ATDMA system may implement a radio technology such as Global System forMobile Communications (GSM).

An OFDMA system may implement a radio technology such as Ultra MobileBroadband (UMB), Evolved UTRA (E-UTRA), Institute of Electrical andElectronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE802.20, Flash-OFDM, etc. UTRA and E-UTRA are part of Universal MobileTelecommunications System (UMTS). LTE and LTE-A are releases of UMTSthat use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, NR, and GSM aredescribed in documents from the organization named “3rd GenerationPartnership Project” (3GPP). CDMA2000 and UMB are described in documentsfrom an organization named “3rd Generation Partnership Project 2”(3GPP2). The techniques described herein may be used for the systems andradio technologies mentioned above as well as other systems and radiotechnologies. While aspects of an LTE or an NR system may be describedfor purposes of example, and LTE or NR terminology may be used in muchof the description, the techniques described herein are applicablebeyond LTE or NR applications.

In LTE/LTE-A networks, including such networks described herein, theterm evolved node B (eNB) may be generally used to describe the basestations. The wireless communications system or systems described hereinmay include a heterogeneous LTE/LTE-A or NR network in which differenttypes of eNBs provide coverage for various geographical regions. Forexample, each eNB, next generation NodeB (gNB), or base station mayprovide communication coverage for a macro cell, a small cell, or othertypes of cell. The term “cell” may be used to describe a base station, acarrier or component carrier associated with a base station, or acoverage area (e.g., sector, etc.) of a carrier or base station,depending on context.

Base stations may include or may be referred to by those skilled in theart as a base transceiver station, a radio base station, an accesspoint, a radio transceiver, a NodeB, eNodeB (eNB), gNB, Home NodeB, aHome eNodeB, or some other suitable terminology. The geographic coveragearea for a base station may be divided into sectors making up only aportion of the coverage area. The wireless communications system orsystems described herein may include base stations of different types(e.g., macro or small cell base stations). The UEs described herein maybe able to communicate with various types of base stations and networkequipment including macro eNBs, small cell eNBs, gNBs, relay basestations, and the like. There may be overlapping geographic coverageareas for different technologies.

A macro cell generally covers a relatively large geographic area (e.g.,several kilometers in radius) and may allow unrestricted access by UEswith service subscriptions with the network provider. A small cell is alower-powered base station, as compared with a macro cell, that mayoperate in the same or different (e.g., licensed, unlicensed, etc.)frequency bands as macro cells. Small cells may include pico cells,femto cells, and micro cells according to various examples. A pico cell,for example, may cover a small geographic area and may allowunrestricted access by UEs with service subscriptions with the networkprovider. A femto cell may also cover a small geographic area (e.g., ahome) and may provide restricted access by UEs having an associationwith the femto cell (e.g., UEs in a closed subscriber group (CSG), UEsfor users in the home, and the like). An eNB for a macro cell may bereferred to as a macro eNB. An eNB for a small cell may be referred toas a small cell eNB, a pico eNB, a femto eNB, or a home eNB. An eNB maysupport one or multiple (e.g., two, three, four, and the like) cells(e.g., component carriers).

The wireless communications system or systems described herein maysupport synchronous or asynchronous operation. For synchronousoperation, the base stations may have similar frame timing, andtransmissions from different base stations may be approximately alignedin time. For asynchronous operation, the base stations may havedifferent frame timing, and transmissions from different base stationsmay not be aligned in time. The techniques described herein may be usedfor either synchronous or asynchronous operations.

The downlink transmissions described herein may also be called forwardlink transmissions while the uplink transmissions may also be calledreverse link transmissions. Each communication link describedherein—including, for example, wireless communications system 100 and200 of FIGS. 1 and 2—may include one or more carriers, where eachcarrier may be a signal made up of multiple sub-carriers (e.g., waveformsignals of different frequencies).

The description set forth herein, in connection with the appendeddrawings, describes example configurations and does not represent allthe examples that may be implemented or that are within the scope of theclaims. The term “exemplary” used herein means “serving as an example,instance, or illustration,” and not “preferred” or “advantageous overother examples.” The detailed description includes specific details forthe purpose of providing an understanding of the described techniques.These techniques, however, may be practiced without these specificdetails. In some instances, well-known structures and devices are shownin block diagram form in order to avoid obscuring the concepts of thedescribed examples.

In the appended figures, similar components or features may have thesame reference label. Further, various components of the same type maybe distinguished by following the reference label by a dash and a secondlabel that distinguishes among the similar components. If just the firstreference label is used in the specification, the description isapplicable to any one of the similar components having the same firstreference label irrespective of the second reference label.

Information and signals described herein may be represented using any ofa variety of different technologies and techniques. For example, data,instructions, commands, information, signals, bits, symbols, and chipsthat may be referenced throughout the above description may berepresented by voltages, currents, electromagnetic waves, magneticfields or particles, optical fields or particles, or any combinationthereof.

The various illustrative blocks and modules described in connection withthe disclosure herein may be implemented or performed with ageneral-purpose processor, a DSP, an ASIC, an FPGA or other programmablelogic device, discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. A general-purpose processor may be a microprocessor,but in the alternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices (e.g., a combinationof a DSP and a microprocessor, multiple microprocessors, one or moremicroprocessors in conjunction with a DSP core, or any other suchconfiguration).

The functions described herein may be implemented in hardware, softwareexecuted by a processor, firmware, or any combination thereof. Ifimplemented in software executed by a processor, the functions may bestored on or transmitted over as one or more instructions or code on acomputer-readable medium. Other examples and implementations are withinthe scope of the disclosure and appended claims. For example, due to thenature of software, functions described above can be implemented usingsoftware executed by a processor, hardware, firmware, hardwiring, orcombinations of any of these. Features implementing functions may alsobe physically located at various positions, including being distributedsuch that portions of functions are implemented at different physicallocations. Also, as used herein, including in the claims, “or” as usedin a list of items (for example, a list of items prefaced by a phrasesuch as “at least one of” or “one or more of”) indicates an inclusivelist such that, for example, a list of at least one of A, B, or C meansA or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, asused herein, the phrase “based on” shall not be construed as a referenceto a closed set of conditions. For example, an exemplary block that isdescribed as “based on condition A” may be based on both a condition Aand a condition B without departing from the scope of the presentdisclosure. In other words, as used herein, the phrase “based on” shallbe construed in the same manner as the phrase “based at least in parton.”

Computer-readable media includes both non-transitory computer storagemedia and communication media including any medium that facilitatestransfer of a computer program from one place to another. Anon-transitory storage medium may be any available medium that can beaccessed by a general purpose or special purpose computer. By way ofexample, and not limitation, non-transitory computer-readable media maycomprise RAM, ROM, electrically erasable programmable read only memory(EEPROM), compact disk (CD) ROM or other optical disk storage, magneticdisk storage or other magnetic storage devices, or any othernon-transitory medium that can be used to carry or store desired programcode means in the form of instructions or data structures and that canbe accessed by a general-purpose or special-purpose computer, or ageneral-purpose or special-purpose processor. Also, any connection isproperly termed a computer-readable medium. For example, if the softwareis transmitted from a website, server, or other remote source using acoaxial cable, fiber optic cable, twisted pair, digital subscriber line(DSL), or wireless technologies such as infrared, radio, and microwave,then the coaxial cable, fiber optic cable, twisted pair, DSL, orwireless technologies such as infrared, radio, and microwave areincluded in the definition of medium. Disk and disc, as used herein,include CD, laser disc, optical disc, digital versatile disc (DVD),floppy disk and Blu-ray disc where disks usually reproduce datamagnetically, while discs reproduce data optically with lasers.Combinations of the above are also included within the scope ofcomputer-readable media.

The description herein is provided to enable a person skilled in the artto make or use the disclosure. Various modifications to the disclosurewill be readily apparent to those skilled in the art, and the genericprinciples defined herein may be applied to other variations withoutdeparting from the scope of the disclosure. Thus, the disclosure is notlimited to the examples and designs described herein, but is to beaccorded the broadest scope consistent with the principles and novelfeatures disclosed herein.

What is claimed is:
 1. A method for wireless communication at a sourceaccess and mobility management function (AMF), comprising: determiningto modify current-allowed network slices supported for a user equipment(UE) based at least in part on a network-trigger; identifying anew-allowed network slice supported for the UE based at least in part onthe determining; determining that the source AMF is unable to serve thenew-allowed network slice; transmitting an indication to the UE toinitiate a registration procedure, based at least in part on thedetermining that the source AMF is unable to serve the new-allowednetwork slice; selecting a target AMF based at least in part on thetransmitting, wherein the target AMF is associated with the new-allowednetwork slice; and triggering an AMF relocation based at least in parton the selecting.
 2. The method of claim 1, further comprising:determining that the UE has an active network slice instance (NSI)associated with at least one network selection assistance information(NSSAI); and identifying that an active NSI is supported by thenew-allowed network slices.
 3. The method of claim 2, furthercomprising: generating a status report indicating a status of allexisting protocol data unit (PDU) sessions associated with the activeNSI.
 4. The method of claim 2, wherein triggering the AMF relocationfurther comprising: transmitting an AMF relocation request to the targetAMF based at least in part on the new-allowed network slices, whereinthe AMF relocation request comprises a status of all existing PDUsession associated with the active NSI that are supported and active, ora new radio (NR) globally unique temporary identifier (GUTI), or both.5. The method of claim 1, further comprising: triggering a releaseprocedure of an active protocol data unit (PDU) session associated withthe current-allowed network slices based at least in part on identifyingthat the active PDU session is unsupported by the new-allowed networkslices.
 6. The method of claim 5, wherein triggering the releaseprocedure is based at least in part on direct signaling to the UE. 7.The method of claim 1, further comprising: determining to modifycurrent-allowed network slices used by a UE based at least in part on areceived network-trigger; identifying new-allowed network slices for theUE based at least in part on the determining; and determining that atarget AMF associated with the new-allowed network slices isinaccessible by the source AMF.
 8. The method of claim 7, furthercomprising: transmitting a de-registration request to the UE based atleast in part on determining that the target AMF is inaccessible by thesource AMF.
 9. The method of claim 8, wherein the de-registrationrequest comprises an indication to perform a re-registration procedure,the new-allowed network slices, or a code indicating that thede-registration request is in response to a change of supported networkslices, or a combination thereof.
 10. The method of claim 8, furthercomprising: triggering a release procedure of an active protocol dataunit (PDU) session associated with current-allowed network slices thatare unsupported by the new-allowed network slices; and releasing UEcontext comprising a status report of active PDU session or a new radio(NR) globally unique temporary identifier (GUTI), or both based at leastin part on the triggering.
 11. A method for wireless communication at auser equipment (UE), comprising: receiving, from a source access andmobility management function (AMF), a configuration message comprisingan identifier associated with a target AMF, a status of existing activeprotocol data unit (PDU) sessions of the UE, a new-allowed networkslice, or an indication to initiate a registration procedure, or acombination thereof; initiating a registration procedure based at leastin part on the receiving; identifying an active PDU session based atleast in part on the receiving, wherein the active PDU session isunsupported by the new-allowed network slice; and locally releasing theactive PDU session based at least in part on the initiating.
 12. Themethod of claim 11, wherein the identifier comprises a new radio (NR)globally unique temporary identifier (GUTI).
 13. The method of claim 11,further comprising: identifying a re-registration request and a codeindicating a request to register a set of network slices associated witha new-allowed network slice based at least in part on a receivedde-registration request from a source access and management function(AMF) that is serving the UE; identifying the new-allowed network slicesbased at least in part on the received de-registration request.
 14. Themethod of claim 13, further comprising: generating a request forregistering the set of network slices associated with a new-allowednetwork slice based at least in part on the code, wherein the initiatingis associated with the generating.
 15. The method of claim 13, furthercomprising: storing information associated with the new-allowed networkslices, wherein the information comprises NSSAI.
 16. A method forwireless communication at an access network (AN), comprising: receiving,from a user equipment (UE), a radio resource control (RRC) connectionrequest comprising network slice selection assistance information(NSSAI); identifying a source access and management function (AMF)associated with current-allowed network slices of the UE based at leastin part on the NSSAI; determining to modify the NSSAI based at least inpart on a trigger indication; identifying a new-allowed network slicesupported for the UE based at least in part on the determining;determining that the source AMF is unable to serve the new-allowednetwork slice; receiving a request to initiate a re-registrationprocedure based at least in part on the source AMF being unable to servethe new-allowed network slice; selecting a target AMF to serve the UEbased at least in part on the request; and triggering an AMF relocationbased at least in part on the selecting.
 17. The method of claim 16wherein signaling the source AMF comprises: transmitting an indicationcomprising information for selection of the target AMF for redirectingthe RRC connection request; and transmitting instructions for performingthe redirecting via the source AMF.
 18. The method of claim 17, whereinthe instructions for performing the redirecting correspond to signalingbetween the source AMF and the target AMF via the AN.
 19. The method ofclaim 17, wherein the instructions for performing the redirectingcorrespond to signaling between the source AMF and the target AMF viadirect signaling.
 20. The method of claim 16, wherein the triggerindication comprises a policy control function (PCF) indication, anindication designating a change in a subscription of one or morecurrent-allowed network slices, or a combination thereof.
 21. The methodof claim 16, further comprising: establishing an N2 signaling connectionwith the target AMF; and transmitting a NAS message received from the UEto the target AMF using the N2 signaling connection.
 22. The method ofclaim 21, further comprising: transmitting, to the source AMF, a requestto release an N2 signaling connection.
 23. The method of claim 21,further comprising: receiving, from the target AMF, an updated NRglobally unique temporary identifier (GUTI) for the UE; and replacing aprevious NR GUTI with the received updated NR GUTI for the UE.
 24. Amethod for wireless communication at an access network (AN), comprising:determining to modify the network slice selection assistance information(NSSAI) based at least in part on a trigger indication; identifying anew-allowed network slice supported for the UE based at least in part onthe determining; determining that a source access and managementfunction (AMF) associated with current-allowed network slices is unableto serve the new-allowed network slice; identifying a re-registrationrequest; selecting a target AMF to serve the UE based at least in parton the re-registration request, wherein the target AMF is associatedwith the new-allowed network slice; and triggering an AMF relocationbased at least in part on the selecting, wherein the AMF relocationcomprises initiating a redirection of the UE from the source AMF to thetarget AMF.
 25. The method of claim 24, wherein the request forrelocation comprises context information for at least one of thenew-allowed network slices, the UE, or the target AMF.
 26. The method ofclaim 24, further comprising: receiving, from the target AMF, an updatedNR globally unique temporary identifier (GUTI) for the UE; and replacinga previous NR GUTI with the received updated NR GUTI for the UE.
 27. Themethod of claim 24, further comprising: transmitting, to the UE, aconfiguration request message comprising the updated NR GUTI, a statusof existing active protocol data unit (PDU) sessions of the UE,indication of the modifying to the NSSAI, or a combination thereof. 28.The method of claim 24, wherein the trigger indication comprises apolicy control function (PCF) indication, an indication designating achange in a subscription of one or more current-allowed network slices,or a combination thereof.
 29. The method of claim 24, wherein theredirection of the UE is based at least in part on an operator policy.30. The method of claim 1, wherein the indication to the UE to initiatea registration procedure comprises an indication to perform are-registration request.